My opinion: http://rustyrazorblade.com/2013/09/cassandra-faq-can-i-start-with-a-single-node/
TL;DR: the only reason to run 1 node in prod is if you're super broke but know you'll need to scale up almost immediately after going to prod (maybe after getting some funding). If you're planning on doing it as a more permanent solution, you've chosen the wrong database. On Fri, Jan 22, 2016 at 12:30 PM Jack Krupansky <jack.krupan...@gmail.com> wrote: > The risks would be about the same as with a single-node Postgres or MySQL > database, except that you wouldn't have the benefit of full SQL. > > How much data (rows, columns), what kind of load pattern (heavy write, > heavy update, heavy query), and what types of queries (primary key-only, > slices, filtering, secondary indexes, etc.)? > > -- Jack Krupansky > > On Fri, Jan 22, 2016 at 3:24 PM, John Lammers < > john.lamm...@karoshealth.com> wrote: > >> After deploying a number of production systems with up to 10 Cassandra >> nodes each, we are looking at deploying a small, all-in-one-server system >> with only a single, local node (Cassandra 2.1.11). >> >> What are the risks of such a configuration? >> >> The virtual disk would be running RAID 5 and the disk controller would >> have a flash backed write-behind cache. >> >> What's the best way to configure Cassandra and/or respecify the hardware >> for an all-in-one-box solution? >> >> Thanks-in-advance! >> >> --John >> >> >
