When we start using cassandra in our company, we decide to use a single node Cassandra cluster as PoC. Everything was correct until we really need the power of a Cassandra cluster and then our data models were not appropriate for a cluster with multiple nodes because of redundancy, data access patterns, etc…
At the end, we install a cluster and we refactor our data model. Today we still maintain that single node cluster with legacy data which cannot be deleted and we do not have time to migrate. And this is an overhead for the system administrators and for developers because every new feature need to work against the legacy and the proper data model. If you really think you need Cassandra because of the high availability and because you are going to store a lot of data, then it is better in my opinion to reject the idea of a single node cluster. From: Bhupendra Baraiya [mailto:bhupendra.bara...@continuum.net] Sent: woensdag 6 april 2016 15:45 To: user@cassandra.apache.org Subject: Cassandra Single Node Setup Questions Hi , I had few question related to Single Node Setup in Cassandra 1) We want to install Cassandra but multiple Node is not what we need Can we proceed with Single Node and store millions of data in Single Node only 2) How many Partitions are allowed per Node , that is what is the limit of Partition in single node if exceeded will impact the Performance 3) How many rows allowed per Partition in Single Node Thanks and regards, Bhupendra Baraiya Continuum Managed Services, LLC. p: 902-933-0019 e: bhupendra.bara...@continuum.net<mailto:bhupendra.bara...@continuum.net> w: continuum.net [cid:image001.png@01D19020.921025A0]<http://www.continuum.net/>
