If I had to choose between running 3x docker instances and 1x instance on a single server, I'd choose the single one. Instead of dealing with RF changing nonsense I'd just set up a 2nd data center w/ 3 nodes and move to that when you're ready. No downtime, easy.
With that said - Starting off with a 3 node cluster in digital ocean is pretty inexpensive. You can be up and running for $60 a month. You should also ask yourself if you have a Cassandra problem. It's designed to scale out to hundreds of nodes, you're talking about 1. Do you think you'll actually have a big data problem, or are you just trying to prepare for the future? On Tue, Dec 15, 2015 at 11:04 AM Robert Coli <rc...@eventbrite.com> wrote: > On Mon, Dec 14, 2015 at 10:53 PM, Vladimir Prudnikov < > v.prudni...@gmail.com> wrote: > >> Is it hard to start with 3 nodes on one server running in docker and then >> just move 2 nodes to the separate servers? >> > > FWIW, if you *absolutely knew* that you were going to need the scale and > for some reason could not convince the money people of this obvious truth, > there is nothing especially wrong with running a Cassandra node in this > manner. It's really inefficient but does allow you to expand a cluster > beyond one node without having to deal with the implications of increasing > RF. > > =Rob > PS - Note that I am still very skeptical that a meaningful number of > people are in this case, almost everyone in a case like this should "just > use MySQL." > >
