Ali, An RDBMS is solving a different problem than Cassandra is so its an apples to oranges comparison from where I sit. If you don't need Cassandra (which sounds like you do), then don't use it -- more nodes and higher tiers of AWS are a function of the features it offers. Imagine what your costs would be with an RDBMS with an attempt to replicate the features of Cassandra?
- Dimitry On Thu, Jun 15, 2017 at 10:17 AM, Ali Akhtar <ali.rac...@gmail.com> wrote: > A client recently inquired about the costs of running Cassandra vs a > traditional RDBMS like Postgres or Mysql, in the cloud. > > They are releasing a b2b product similar to Slack, Trello, etc which will > have a free tier. And they're concerned about the costs of running it on > Cassandra, and whether it may be too expensive if it gets popular. > > They have a write heavy workload, where data is being received 24/7, > analyzed and the results written to Cassandra. A few times a day, users > will view the results of the analysis, which will be the read portion of > the system. > > Its my understanding that it may cost slightly, e.g 10-15% more to run > this system on Cassandra vs an RDBMS, because it needs more nodes, and > higher tier of AWS / GCE instances to run. > > Can anyone who has experience scaling Cassandra share their insights? > > Costs, metrics (e.g users, requests per second), etc would be really > helpful! >
