Jeff, that may be true for many ... but for our application, the performance of a single Cassandra node blows the doors off Oracle and PostgreSQL.
On Fri, Jan 22, 2016 at 4:24 PM, Jeff Jirsa <jeff.ji...@crowdstrike.com> wrote: > The value of cassandra is in its replication – as a single node solution, > it’s slower and less flexible than alternatives > > > From: John Lammers > Reply-To: "user@cassandra.apache.org" > Date: Friday, January 22, 2016 at 12:57 PM > To: Cassandra Mailing List > > Subject: Fwd: Production with Single Node > > Thanks for your reply Sebastian. > > They are specialized data storage & retrieval systems. The Cassandra > database is mainly used to store meta-data for searching. > > Jonathan, I had seen your article. But what are some of the technical > reasons why a one node Cassandra cluster is a bad idea? I need ammo to > convince others. Or failing that, what can be done to make this > configuration as safe & robust as possible? > > Thanks! > > --John > > ---------- Forwarded message ---------- > From: Sebastian Estevez <sebastian.este...@datastax.com> > Date: Fri, Jan 22, 2016 at 3:41 PM > Subject: Fwd: Production with Single Node > To: john.lamm...@karoshealth.com > > > Hi John, > > Can you share a bit more about your use case? What's the purpose of these > little clusters? Jon has good points but I'm cautious to dismiss your idea > without hearing specifics about your plans. > > > All the best, > > > [image: datastax_logo.png] <http://www.datastax.com/> > > Sebastián Estévez > > Solutions Architect |954 905 8615 | sebastian.este...@datastax.com > > [image: linkedin.png] <https://www.linkedin.com/company/datastax>[image: > facebook.png] <https://www.facebook.com/datastax>[image: twitter.png] > <https://twitter.com/datastax>[image: g+.png] > <https://plus.google.com/+Datastax/about> > <http://feeds.feedburner.com/datastax> > <http://goog_410786983> > > > <http://www.datastax.com/gartner-magic-quadrant-odbms> > > DataStax is the fastest, most scalable distributed database technology, > delivering Apache Cassandra to the world’s most innovative enterprises. > Datastax is built to be agile, always-on, and predictably scalable to any > size. With more than 500 customers in 45 countries, DataStax is the > database technology and transactional backbone of choice for the worlds > most innovative companies such as Netflix, Adobe, Intuit, and eBay. > > ---------- Forwarded message ---------- > From: Jack Krupansky <jack.krupan...@gmail.com> > Date: Fri, Jan 22, 2016 at 3:30 PM > Subject: Re: Production with Single Node > To: user@cassandra.apache.org > > > 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 >> >> > > >
