Hi all -
We currently have a single cassandra cluster that is dedicated to a
relatively narrow purpose, with just 2 tables. Soon we will need cassandra
for another, unrelated, system, and my debate is whether to just add the
new tables to our existing cassandra cluster or whether to spin up an
Adding a new keyspace should be perfectly fine. Unless you have completely
distinct workloads for the different keyspaces. Even so you can balanced
some stuff at keyspace/table level. But I would go with a new keyspace not
with a new cluster given the small size you say you have.
Regards,
Carlos
Thanks for the input, folks!
As a startup, we don't really have different dev teams / apps - everything
is in service of the product, so given these responses, I think putting
both into the same cluster is the best idea. And if we want to split them
out in the future we are still small enough
There is an old saying in the software industry: The structure of a system
follows from the structure of the organization that created it (Conway's
Law). Seriously, the main, first question for your end is who owns the
applications in terms of executive management, such that if management
makes a
Jack did a superb job of explaining all of your issues, and his last
sentence seems to fit your needs (and my experience) very well. The only
other point I would add is to ascertain if the use patterns commend
microservices to abstract from data locality, even if the initial
deployment is a noop
