Autoscaling plan for IoTDB (e.g. on Azure)
- Vorherrschende Sprache
- Java
- Sterne
- 6.4k
- Forks
- 1.2k
- Ø Merge
- 1 T. 23 Std.
- Gemergte PRs (30 T.)
- 115
Beschreibung
**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.
Beitragsleitfaden
Rechercherichtung
Beginne mit der vorhandenen Dokumentation zu Hadoop Cluster und untersuche von Azure verwaltete Alternativen, einschließlich VM scale sets und verwaltetem Speicher. Ermittle, ob eine autoskalierende IoTDB-Bereitstellung praktikabel ist, und dokumentiere ein konkretes Azure-Beispiel einschließlich des Speicheransatzes, des Skalierungsverhaltens und der relevanten Abwägungen.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- azure, hadoop
- Bereich
- cloud, databases, documentation
- Issue-Typ
- Dokumentation
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 25/100