Autoscaling plan for IoTDB (e.g. on Azure)
- Lenguaje dominante
- Java
- Estrellas
- 6.4k
- Forks
- 1.2k
- Merge medio
- 1 d 23 h
- PR fusionados (30 d)
- 115
Descripción
**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.
Guía de contribución
Línea de trabajo
Comienza con la documentación existente de Hadoop Cluster e investiga alternativas administradas por Azure, incluidos VM scale sets y el almacenamiento administrado. Determina si es viable una implementación de IoTDB con autoscaling y documenta un ejemplo concreto en Azure, incluido el enfoque de almacenamiento, el comportamiento del escalado y las ventajas y desventajas relevantes.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- azure, hadoop
- Área
- cloud, databases, documentation
- Tipo de issue
- Documentación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Estado de actividad
- Estancado
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 25/100