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



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

PaaS on Hadoop Yarn - Idea and Prototype

Related to the earlier Hadoop YARN, Beyond MapReduce, here’s a very interesting experiment by the SAP Labs:

This post describes a prototype implementation of a simple PAAS built on the Hadoop YARN framework and the key findings from the experiment. While there are some advantages to using Hadoop YARN, there is at least one unsolved issue that would be difficult to overcome at this point.


Code of this experiment was made available on GitHub.

Original title and link: PaaS on Hadoop Yarn - Idea and Prototype (NoSQL database©myNoSQL)


Memcached as a Service for Cloud Foundry

After giving its source code a look-over, I noticed that the important component is missing - Memcached. Memcached is the de facto standard free & open source, high-performance, distributed memory object caching system, as you know. The other PaaS also supports Memcached (ex. Google App Engine, Heroku, Amazon Web Service, and so on) in various way. I believe that a lot of PaaS users want to use Memcahced, therefore, I decided to implement Memcached as a Service for Cloud Foundry.

The Java world isn’t so big into Memcached. But that’s not a good excuse for not having support for Memcahed in Cloud Foundry.

Original title and link: Memcached as a Service for Cloud Foundry (NoSQL database©myNoSQL)


MongoDB Selected as Core Content Management Component of SAP's Platform-As-A-Service

MongoDB will be utilised initially for collaborative decision making, data archiving and retention management in a multi-tenant and secure environment. MongoDB will be used as the document-oriented store for SAP’s on-demand applications, delivering lower cost of ownership and increased stability.

“MongoDB offers scalability and flexibility at a total cost of ownership that enables us to deliver applications to our customers at affordable prices,” said Harald Mueller, chief product owner, Java Platform, SAP. “We need to deliver applications that meet our customers’ needs now and in the future as they grow their business. MongoDB plays a crucial role in our ability to do that. We’re excited about the possibilities and look forward to further use of MongoDB in the future.”

While I couldn’t find any clear details of the SAP PaaS offering, this is nonetheless another confirmation of the maturity some of the NoSQL databases have achieved in just a few years.

Original title and link: MongoDB Selected as Core Content Management Component of SAP’s Platform-As-A-Service (NoSQL database©myNoSQL)


Sinatra with Redis on Cloud Foundry

The workshop takes you through creating a Sinatra application using sample code from here . Once the Sinatra application which leverages Twitter is working, the workshop then takes you through adding Redis to your application. Finally the workshop ends after taking you through scaling your application instances up and then back down.

Only 15 minutes to get it up and running:

Original title and link: Sinatra with Redis on Cloud Foundry (NoSQL databases © myNoSQL)

Cloud Foundry, NoSQL Databases, and Polyglot Persistence

VMWare’s Cloud Foundry has the potential to become the preferred PaaS solution. It bundles together a set of services that it took years for other PaaS providers (Google App Engine, Microsoft Azure) to offer. And it seems that Cloud Foundry has much less (or none at all) vendor lock in[1].

From a storage perspective, Cloud Foundry is encouraging polyglot persistence right from the start offering access to a relational database (MySQL), a super-fast smart key-value store (Redis), and a popular document database (MongoDB). The only bit missing is a graph database[2].

I think the first graph database to get there will see an immediate bump in its adoption.

  1. These comments are based on what I’ve read about VMWare CloudFoundry as I haven’t received (yet) my invitation.  

  2. I don’t think wide-column databases (Cassandra, HBase) are fit for PaaS  

Original title and link: Cloud Foundry, NoSQL Databases, and Polyglot Persistence (NoSQL databases © myNoSQL)