Generally, regardless of your expected cluster size, you need to perform a proof of concept implementation (POC) to obtain those numbers for your own application. These numbers are not absolute limits enforced by Cassandra, but practical limits based on your actual data model, actual data patterns, and actual access patterns, as well as your actual hardware - RAM, storage (SSD vs. HDD), and network connectivity. And queries drive the data modeling - how do you intend to access the data, latency requirements, and how many concurrent clients do you expect.
Generally, Cassandra is chosen for applications which have a lot of data and the need for high availability (redundancy, meaning at least three copies of the data.) Neither of which seems to be your requirement. How much data do you have? What led you to believe that you only need a single node? -- Jack Krupansky On Wed, Apr 6, 2016 at 9:44 AM, Bhupendra Baraiya < bhupendra.bara...@continuum.net> wrote: > 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 > > w: continuum.net > > [image: > http://cdn2.hubspot.net/hub/281750/file-393087232-png/img/logos/email-continuum-logo-151x26.png] > <http://www.continuum.net/> > > > > >
