NoSQL Benchmarks NoSQL use cases NoSQL Videos NoSQL Hybrid Solutions NoSQL Presentations Big Data Hadoop MapReduce Pig Hive Flume Oozie Sqoop HDFS ZooKeeper Cascading Cascalog BigTable Cassandra HBase Hypertable Couchbase CouchDB MongoDB OrientDB RavenDB Jackrabbit Terrastore Amazon DynamoDB Redis Riak Project Voldemort Tokyo Cabinet Kyoto Cabinet memcached Amazon SimpleDB Datomic MemcacheDB M/DB GT.M Amazon Dynamo Dynomite Mnesia Yahoo! PNUTS/Sherpa Neo4j InfoGrid Sones GraphDB InfiniteGraph AllegroGraph MarkLogic Clustrix CouchDB Case Studies MongoDB Case Studies NoSQL at Adobe NoSQL at Facebook NoSQL at Twitter



DaaS: All content tagged as DaaS in NoSQL databases and polyglot persistence

The cloud landscape described, categorized, and compared

Fantastic article by Johan Den Haan:

In this article I will explain this framework. I will also explain how I constructed this framework, give some example technologies/solutions for each cell of the framework, and show how this framework can be used to compare some of the popular cloud platforms (e.g. OpenStack, AWS, Heroku, CloudFoundry).


Not only does it provide good details about Database-as-a-Service and even Business Analytics Platform-as-a-Service, but it also shows how these are higher building blocks of object storage and software defined storage.

Original title and link: The cloud landscape described, categorized, and compared (NoSQL database©myNoSQL)


Choosing the right hosting for your database

The Rackspace post is titled “Choosing The Right Cloud Provider For Your MongoDB Database“, as they have a stake in the game. But the chart they’ve put together is generic enough to be useful whenever you have to decide where to host your database:


Original title and link: Choosing the right hosting for your database (NoSQL database©myNoSQL)

Heroku Postgres Rollback

New features available on Heroku’s hosted PostgreSQL

Heroku Postgres rollback allows you to “roll back” the state of your database to a previous point in time, just as heroku releases:rollback allows you to roll back to an older deployment of your application. Rollback does not affect your primary database, but instead follows the same pattern as fork: it provisions a new database that is not directly connected to the primary in any way. Like a fork, a rollback will take some time to become available.

I’d really love to know how this is done1.

  1. I have some vague ideas, but it’s better to learn than to speculate. 

Original title and link: Heroku Postgres Rollback (NoSQL database©myNoSQL)


Rackspace: BYOD to Your Preferred Storage

While Amazon Web Services approach is bring-your-own-data to our storage and processing solutions, Rackspace’s strategy seems to be “whatever popular NoSQL storage engine you like, we have your back. Just bring your data“.

Last month Rackspace bought MongoDB hosting provider ObjectRocket and now they acquired Exceptional Cloud Service which brings Redis hosting on board.

It’s difficult to say how well is Amazon’s strategy working as the company doesn’t do a lot to get their customers’ case studies out there—I still need to find a list of 10 companies that are using Amazon Dynamo. But this doesn’t mean a thing. On the other hand, I can see Rackspace’s strategy working and getting a lot of traction considering they’re looking after the most popular NoSQL tools.

✚ The Register writes about this acquisition too: Rackspace gobbles Exceptional Cloud Services for Redis smarts. I assume many others are asking the same question:

So, with Redis and MongoDB due to make their way into the Rackspace cloud proper, what other technologies are catching the web hoster turned cloud whisperer’s eyes?

Original title and link: Rackspace: BYOD to Your Preferred Storage (NoSQL database©myNoSQL)

The Business of Database as a Service

From a PR announcement about Cloudant’s business results in 2012 :

Cloudant says that during 2012, a year that saw its staff grow to 45 employees, the company’s customer base grew to more than 12,000 multi-tenant customers, counting both free customers, as well as the 50 that pay for its dedicated clusters.

I wholeheartedly hope these results are not indicative for the Database-as-a-Service market. I also wish Cloudant an even better 2013.

I haven’t seen any numbers from major platforms like Amazon Web Services, Heroku, or Rackspace, so if you have any please do share them.

Original title and link: The Business of Database as a Service (NoSQL database©myNoSQL)

Neo Technology Is H… Wait, It’s Building Neo4j-As-A-Service

Neo Technology’s hiring announcement is clear about their intention:

“[…] you will be resonsible for building, managing, and maintaining a 24x7 NOSQL Databases-as-a-Service operation […]”

In the graph databases space, OrientDB is offering a hosting solution NuvolaBase, but I have no numbers about their business so far.

Original title and link: Neo Technology Is H… Wait, It’s Building Neo4j-As-A-Service (NoSQL database©myNoSQL)

Hosted Riak With Riak-On

First let me welcome Riak ON!, the first company planning to offer a hosted Riak solution or Riak-as-a-Service.

Second, I’d like to ask for your help in answering the question that pops into my mind everytime I’m thinking about Data-as-a-Service: leaving aside the benefits of managed services, what are the scenarios in which a Data-as-a-Service can be used when the application layer is not colocated1?

  1. A different way to formulate this question is: what apps can tolerate the WAN latency and network failures? Obviously these questions do not apply to services like Amazon Web Services or Heroku or dotCloud which offer you both Data-as-a-Service and a PaaS or IaaS. 

Original title and link: Hosted Riak With Riak-On (NoSQL database©myNoSQL)

The Database World in a Venn Diagram

Infochimps put together a comprehensive Venn diagram of the database world in the TechCrunch article Big Data Right Now: Five Trendy Open Source Technologies

The Database World

Original title and link: The Database World in a Venn Diagram (NoSQL database©myNoSQL)

Where Does Xeround Fit In The CAP Theorem?

Itamar Haber over the Xeround blog:

Q: Is Xeround Inconsistent? Xeround employs a set of majority-based algorithms to facilitate its reading and writing of data from/to multiple, distributed nodes. […] Via the use of these algorithms we are ensured that all access to the data is consistent so inconsistency is not an issue.

Q: Is Xeround Unavailable? There is no single point of failure in Xeround and every component that the system consists of is redundant and replaceable.

Q: Is Xeround Partitioning-Intolerant? Yes, to a certain extent it is.

After reading it, I got the same impression as VoltDB’s John Hugg who commented:

It sounds like you’ve gotten this backwards. According to you, in the face of a network event, the system becomes unavailable, but remains consistent. I think you have partition tolerance, but with reduced availability.

Instead of focusing strictly on the CAP characteristics of a distributed database, one should focus on what is the required behavior for their system and look for the database solution that offers them the guarantees they need.

Original title and link: Where Does Xeround Fit In The CAP Theorem? (NoSQL database©myNoSQL)