NewSQL versus traditional optimization/sharding [closed] NewSQL versus traditional optimization/sharding [closed] database database

NewSQL versus traditional optimization/sharding [closed]


Not sure if you heard about NuoDB yet. But it is a brand new SQL solution that offers the scale-out capabilities of NoSQL and the SQL & ACID compliance capabilities of traditional OLTP. You should take look at the solution.


At Jingit (www.jingit.com) we have battle tested VoltDB. It is fantastic on scaling write heavy apps and in AWS cloud. There is no hosted option so our devs own it and they spend < 1 hr a week administering our VoltDB cluster. We actually use both RDS and VoltDB. RDS for our traditional relational workload, and VoltDB for our HIGH VOLUME transaction processing. If you are developing in Java, VoltDB is a great fit as you write all the procedures in Java.


I hear, too, that NuoDB is interesting. One thing I hear is that Rackspace is coming out with cloud DBaaS sometime soon as well. I don't know what flavor they'll use, but you could see how Nuo works as a scalable solution with them. I think it'll run in conjunction with the Open Stack platform, which, when they open it up, could be more cost and computationally efficient. Just something I've been eyeballing myself.