The ultimate goal is to connect the open source Stateful Services with FaaS, such as AWS Lambda, Apache OpenWhisk, etc. So data could easily move from application to stateful service, from one stateful service to another stateful service, or from stateful service to application.
The release plans are briefly described here. For the full list of features and fixes of one release, please refer to the release docs.
The plan will be adjusted by the requirements. If you prefer to have some other features, please feel free to open an issue or join slack to propose your idea.
- Initial Monitoring support for Cassandra, Kafka, ZooKeeper & Redis
- Support Upgrade from 0.9.4
- Initial work to connect Kafka to ElasticSearch
- Code refactoring to decouple the catalog services from the core platform.
- Separate the catalog service from the management service.
- Bug fix and enhancements.
The near term features will be included in the coming releases. The detail plan will be finalized soon.
- Further enhance upgrade.
- Monitor more services
- Security: add SSL/TLS for FireCamp management service
- Service Scale: Kafka, ZooKeeper, etc
- Fully support Kubernetes on AWS
- Enhance Kafka auto-connector to ElasticSearch
- Data Management: data snapshot, backup, recovery
- Automatic Data Pipelines
- Support Microsoft Azure, Google Cloud Platform
- Support on-premise Kubernetes
- Support more stateful services
- Geo Access and Protection
- Support open source FaaS engines, such as Apache OpenWhisk
- Connect stateful services with FaaS
- Automatic Data Workflow
- Hybrid Cloud