you're reading...

Founders BLOG

Cloud Database Comparison

I went to a GSLUG meeting last Sat and gave a talk about ClouSE. The slides are mostly the same as here, with the addition of the cloud database technologies comparison chart:

RDBaaS stands for Relational Database as a Service.

Data confidentiality: ClouSE is the only cloud database technology that provides full data confidentiality in the cloud. To guarantee data confidentiality in the cloud ClouSE encrypts the data using military grade AES-256 encryption before it puts the data to the cloud storage. This ensures that the data is visible neither over the wire nor to the cloud storage provider. The data confidentiality is fully controlled with the encryption key that the customer provides to ClouSE. Customers are in charge of encryption key management and fully control who has access to their data, if anyone.

Fast DB access: ClouSE can run on the same machine as the server application (e.g. Web Server), so access from the server application to the database is fast and reliable. Other cloud databases need to be accessed over the Internet, so the server applications need to be re-designed to deal with longer response times and higher failure rates when accessing the database. Most server applications are designed to assume that database access is fast and reliable; ClouSE fully supports that assumption.

ACID transactions, Secondary indices, SQL: NoSQL services don’t support ACID transactions, secondary indices or structured queries. Both ClouSE and RDBaaS provide standard, well-known and widely used relational database management.

Storage elasticity: With RDBaaS, the primary storage size needs to be specified upfront. Users are charged for reserved storage, not for used storage. The storage consumption cannot shrink even if some of the data is deleted. With ClouSE and NoSQL services, the storage consumption grows and shrinks with the amount data, users pay only for storage they use.

Automatic scale out: I put a yellow dot for the automatic scale out for ClouSE to reflect its ability to scale out content delivery from cloud storage directly. Applications that manage a lot of content (e.g. images, videos) may achieve significant scale-out.

Have we missed any important dimensions? Please let us know what other comparisons you are interested in.


3 Responses to “Cloud Database Comparison”

  1. Some pretty big generalizations here, for example RDBaaS not offering auto-scale.

    MySQL Cluster for example supports auto-sharding with on-line scale out, on-demand:

    Posted by Mat Keep | March 14, 2012, 12:56 am
  2. The comparison is always tricky, and I tried my best to do an apples-to-apples comparison of ClouSE to similar technologies in its class.

    Our key value prop is that ClouSE makes existing MySQL-based solutions work better: any MySQL-based solution (cloud or on-premise, clustered or standalone) may be powered by ClouSE and achieve better scalability and availability.

    The comparison is more about RDBMS with ClouSE vs. RDBMS without ClouSE (rather than ClouSE vs. RDBMS). That is, if you got a clustered solution, the one powered by ClouSE would be more scalable and available (because each node is going to be more scalable and available) than one without it.

    In the end, a small comparison chart cannot represent all possible solutions and variations available, it’s just a high-level overview and I encourage everyone to email us with any questions or just simply try ClouSE free at

    Posted by Artem Livshits | March 14, 2012, 12:46 pm


  1. [...] Artem Livshits shares a useful cloud database technologies comparison chart. [...]

Post a Comment


Twitting ...