Dynomite-manager is a Java process/tool that can be used alongside Dynomite to manage a Dynomite cluster. Some of the features include:
- Discovery and Instance Healthcheck
- Node Configuration and Token Management for multi-region deployments
- Dynamic,Typed Properties based on Archaius 2 -- High throughput and Thread Safe Configuration operations.
- Dynomite/Redis cold bootstrap (warm-up)
- Monitoring and Insights Integration
- Support multi-region Dynomite deployment via public IP.
- Automated security group update in a multi-region environment.
- Object storage backups (AWS S3 implementation provided)
- REST API
Details about the features can be found in the Wiki
The stable version of Dynomite-manager is the master branch.
For questions or contributions, please consider reading CONTRIBUTING.md.
Dynomite-manager comes with a Gradle wrapper
The gradlew script will pull down all necessary gradle components/infrastructure automatically, then run the build.
Dynomite-manager provides several default implementations (AWS, Configuration, credentials etc). You can use these or choose to create your own. Dynomite-manager is currently working on AWS and your local environment. We are open to contributions to support other platforms as well.
At Netflix, we use AWS to deploy Dynomite-manager in an EC2 instance along with Dynomite and Redis. However, Dynomite-manager has a set of abstracted interfaces that it can work in different environments. The following are the AWS bindings. In a different environment, these interfaces must be implemented. By default, we provide a local binding for getting the instance information from a local-end point.
Secondly, we use Dynomite-manager as a sidecar for the communication of Dynomite with the highly avalaible database where the tokens are stored. For that reason, we use Cassandra. The default instance factory binding is about Cassandra but any other data store could be used. Moreover, in order to get the information about the Cassandra nodes, we provide a Local Host supplier as well as implementations for Eureka discovery service.
Deploying in a Tomcat Container
- Build the dynomite-manager
- Set up Auto-Scale Group (ASG) and spin up instances
- Install Dynomite and web container (such as tomcat) on the instances.
- Setup AWS credentials
dynomite-manager.warin your container
Integrating with other systems
Dynomite-manager also publishes the corresponding .jars that one can use to integrate with their own systems. At Netflix, we do use this approach. We bring the OSS .jars in our build process that produces a .war file.
Dynomite-manager is comprised of 4 configuration interfaces.
- FloridaConfig: Configuration for everything related to Dynomite and Redis.
- AwsCommonConfig: AWS configuration. If DM is deployed in another environment, then the corresponding interface should be added.
- CassCommonConfig: Cassandra configuration. This is the configuration for Cassandra which stores the Dynomite tokens. If another DB is used, then the corresponding interface should be added.
- CommonConfig: Baseline configuration.
We are looking forward in your contributions. If you need some help with either getting up and going or some problems with the code?
Licensed under the Apache License, Version 2.0: http://www.apache.org/licenses/LICENSE-2.0