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



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

Sharding with SQL Azure

Just after posting about this excellent and SQL Azure comparison, I have found another interesting Microsoft Azure article.

It is about Sharding with SQL Azure and is covering aspects as principles, challenges, and common patterns for horizontal partitioning, a high level design of an ADO.NET sharding library, and an intro to SQL Azure Federations:

The proposed implementation will map data to specific shards by applying one or more strategies upon a “sharding key” which is the primary key in one of the data entities. Related data entities are then clustered into a related set based upon the shared shard key and this unit is referred to as an atomic unit. All records in an atomic unit are always stored in the same shard.

Be aware that the article is quite long, but definitely worth reading.

Original title and link: Sharding with SQL Azure (NoSQL databases © myNoSQL)


Preliminary Comparison of and SQL Azure Features and Capabilities

Extensive comparison of the upcoming and Microsoft’s SQL Azure: will unbundle its underlying relational database engine from when the firm releases’s commercial version in 2011. In the meantime, developers can testdrive with a free developer account, which includes a database having:

  • Three enterprise user accounts
  • 100,000 rows of storage per month
  • 150,000 transactions per month

According to the article, will support ACID transactions (Apex code), triggers and stored procedures (Apex code), relationships, a query language, full-text search. Looks like a relational database in the cloud, but it doesn’t necessarily need to be underneath.

Original title and link: Preliminary Comparison of and SQL Azure Features and Capabilities (NoSQL databases © myNoSQL)


Microsoft coaches NoSQL options for Azure cloud

The Register writing about Microsoft initiative to bring NoSQL databases to the Azure cloud, Membase and MongoDB being mentioned in the article[1]:

The addition of NoSQL suits Microsoft - by bringing more people to Azure - and it suits the NoSQLers, because they get more Windows devs to support.

You can run NoSQL options like Mongo and Memcached on Azure after some fiddling and configuring. The goal now is to deliver a development, deployment, and management experience already familiar to those on Windows, SQL Server, and Visual Basic.

Is VMWare/Spring making the same bet for the Java world? Judging by the Spring Data initiative, plus Grails support for Redis, Grails support for MongoDB, I’d say they are.

A question that I’d like to clarify to myself is how popular is memcached in the Java world? My impression is that Java people have stayed away from memcached so far, using Java based solutions like EHCache or Terracotta, but I might be completely wrong.

Original title and link: Microsoft coaches NoSQL options for Azure cloud (NoSQL databases © myNoSQL)


Microsoft Azure and NoSQL Databases: MongoDB, sones GraphDB, and RavenDB

Looks like today is the day of the NoSQL databases in the Microsoft cloud. After covering how to run MongoDB on Azure and today’s guide to running sones GraphDB on Azure, the third one joining the party is RavenDB:

The short answer was, with the current build, no. RavenDB uses the .NET HttpListener class internally, and apparently that class will not work on worker roles, which are restricted to listening on TCP only.


I have to sign a contribution agreement, and do some more extensive testing, but I hope that Ayende is going to pull my TCP changes into the RavenDB trunk so that this deployment model is supported by the official releases.

So, two document stores and a graph database are already available for Microsoft Azure. Which one is next?

Microsoft Azure and NoSQL Databases: MongoDB, sones GraphDB, and RavenDB originally posted on the NoSQL blog: myNoSQL


sones GraphDB available on Microsoft Windows Azure

sones GraphDB available in the Microsoft cloud:

The sones GraphDB is the first graph database which is available on Microsoft Windows Azure. Since the sones GraphDB is written in C# and based upon Microsoft .NET it can run as an Azure Service in it’s natural environment. No Wrapping, no glue-code. It’s the performance and scalability a customer can get from a on-premise hosted solution paired with the elasticity of a cloud platform.

You can read a bit more about it ☞ here.

In case you’ve picked other graph database, you can probably set it up with one of the cloud providing Infrastructure-as-a-Service.

sones GraphDB available on Microsoft Windows Azure originally posted on the NoSQL blog: myNoSQL

Running MongoDB on ... Microsoft Azure

Very detailed explanation and code on setting up a Windows-based project using MongoDB and running it on Microsoft Azure Blob storage. I confess that Azure doesn’t really sound like the first pick one would make when using MongoDB, but that is exactly what made this article interesting!

I’ve been playing around with the whole CQRS[1] approach and think MongoDb works really well for the query side of things. I also figured it was time I tried Azure so I had a look round the web to see if there we’re instructions on how to run MongoDb on Microsoft’s Azure cloud[2].