How is Cassandra cluster manager different from managing clusters using Kubernetes + containers
Bringing together the Apache Cassandra experts from the community and DataStax.
Want to learn? Have a question? Want to share your expertise? You are in the right place!
Not sure where to begin? Getting Started
This question was
closed
by
Erick Ramirez for the following reason: The question is answered, right answer was accepted
How is CCM different from managing clusters using Kubernetes + containers?
Following on from question #7860 where I explained:
Cassandra Cluster Manager (CCM) is a script that allows users to easily create, manage and destroy a small Cassandra cluster on a local machine. Developers and administrator typically run
ccm on their laptops or desktops so they can quickly run tests against a specific version of a Cassandra cluster.
ccm is a simple script that for launching clusters on a laptop/desktop. It isn't really a cluster "manager". It's just a dev tool that will download a version of open-source Cassandra, configure it with minimal settings (usually sticks to defaults) and installs it -- all in one command.
On the other hand, Kubernetes is a full-featured orchestration tool for managing the full lifecycle of containers in a cluster. It will automate the deployment of containerised applications, scaling, recover when an app instance goes down, monitor and a long list of other management tasks.
There really is no comparison between the two -- one is a script, the other is an enterprise solution. Cheers!
Thanks for the explanation Eric. I noted it down but I forgot to accept the answer.
5 People are following this question.
