Autoscaling plan for IoTDB (e.g. on Azure)
- 主要言語
- Java
- スター
- 6.4k
- フォーク
- 1.2k
- 平均マージ
- 1日 23時間
- マージ済み PR(30日)
- 115
説明
**Is your feature request related to a problem? Please describe.**
At our company, we want to have most of our services as managed services. This makes maintenance very effective on our side as we do not have to employ more people to keep the infrastructure running. Currently this is a blocker for integrating IoTDB, as everything around this database would have to be managed and scaled manually.
**Describe the solution you'd like**
A part of the documentation, describing an example of how to set up IoTDB by using only auto-scaling modules of a cloud provider - for me Azure would be the best example.
**Describe alternatives you've considered**
The documentation already has something about a Hadoop Cluster, which I could find as managed solution on Azure, but I don't know if it's a good solution (price-vise) and if it will scale automatically with our demands.
**Additional context**
Any hint is also very welcome!
As I understand, integrating the storage as a managed storage would already be a huge improvement - like a storage abstraction which is compatible with Azure Storage.
For the IoTDB instance itself my first thought was to set up a VM scale set, which will add new VMs to a cluster as certain limits (e.g. in CPU usage) are reached. If this whole idea of mine is just not the right way, I'm thrilled to get your input.
コントリビューションガイド
調査の方向性
既存の Hadoop Cluster ドキュメントから始め、VM scale sets やマネージドストレージを含む、Azure マネージドの代替手段を調査してください。autoscaling に対応した IoTDB デプロイメントが実現可能かどうかを判断し、ストレージの方式、スケーリング動作、関連するトレードオフを含む具体的な Azure の例を文書化してください。
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- azure, hadoop
- 領域
- cloud, databases, documentation
- issue の種類
- ドキュメント
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 活発さ
- 停滞
- 明瞭さ
- 説明が足りない
- 初心者へのやさしさ
- 25/100