<p>I am using containers to run both app servers &amp; Cassandra nodes.</p>
<p>When starting the app server container, I need to specify which Cassandra node(1..n) to connect to. How would you divide the workload?</p>
<ol>
<li>One app container to one or more Cassandra nodes(How many).</li>
<li>One or more app container to one Cassandra node(How many).</li>
<li>Many to many(How many).</li>
</ol>
<p>This is for a production setup, 100 % uptime. Each data load from cassandra is small but many.<br>
<br>I should be scalable so I can put in more app containers - like in Kubernetes they have pods. Pods is a set of nodes that make up granules of the application.
<br>Therefore I am looking for the best possible group of containers(Cassandra and App server) that will scale
<br><br>
Info: Kubernetes is a to expensive setup in the beginning. And while waiting for Docker Swarm to be in release state I will do this manually. Any insight is welcome?</p>
<p>Regards</p>

Chris G.
<p>Please see:</p>

<p><a href="https://github.com/kubernetes/kubernetes/blob/release-1.0/examples/cassandra/README.md" rel="nofollow">https://github.com/kubernetes/kubernetes/blob/release-1.0/examples/cassandra/README.md</a></p>

<p>for a tutorial of how to run Cassandra on Kubernetes.</p>

<p>You will also need to add in best practices like snapshotting the databases to persistent storage and other such things.</p>

<p>(and why do you say that Kubernetes is expensive?  Google Container Engine only charges the cost of the VMs for small clusters, and you can deploy open source Kubernetes yourself for free)</p>
