An Elastically Scalable Database? Tap the 90 Partner Sam Kumarsamy and NuoDB
Today's surge of Big Data is bringing about the need to handle data in ways far more advanced than conventional solutions. NuoDB is one such company reshaping how systems architects and database engineers deal with today's data requirements. NuoDB is a NewSQL cloud database. It looks and behaves like a traditional SQL database from the outside but under the covers it's a revolutionary database solution.
I met with NuoDB at the NoSQL Now conference in San Jose, Ca., introducing them to the analyst group Tap the 90. On October 11, 2012, I hosted an interview between Tap the 90 Partner Sam Kumarsamy and NuoDB's Michael Waclawiczek, VP of Marketing, and Wiqar Chaudry. Director of Product Marketing.
NuoDB Interview
Sam Kumarsamy/Tap the 90: What is the compelling business value proposition of NuoDB?
Michael Waclawiczek/NuoDB: Both internally and externally we define ourselves as the 21st century SQL database, meeting new requirements that are currently not met by the traditional SQL databases. We are 100 percent SQL and 100 percent ACID compliant. Our uniqueness is in elastic scalability – meaning that the database allows you to add nodes thus adding more throughput to the database. Redundancy is built into the database – every redundant node in our system is a full copy of the database . We are not sharding (partitioning) data and it is a single logical database spanning multiple computing resources.
Sam: How do you differentiate NuoDB from other NewSQL vendors and more specifically from VoltDB and Clustrix . Both also claim they can scale out without partitioning or sharding.
Wiqar Chaudry/NuoDB: That’s not true. VoltDB can scale out and it is an in-memory only database . VoltDB uses Hadoop to persist their data and make it durable. VoltDB does auto sharding and the inherent limitations of auto sharding still exist in VoltDB. For example, if you are sharding a database table that is large in volume across multiple nodes of VoltDB in a cluster, you are essentially pushing the burden of maintaining uniqueness across all of the rows within that table across all the partitions back up at the application layer. That’s inherent in databases that use sharding. What VoltDB is saying is that you don’t have to physically take care of the administration of creating a horizontal partitioned table and they will do it for you. But they are telling you that this will still be the task of the application developer.
Continued on the next page
Follow Technorati