Sort of the basics of MongoDB queries with NoRM, the .NET MongoDB driver:

It provides strongly typed interface around Mongo queries, linq support and very fast serialization from MongoDB documents to .NET CLR objects and vice versa.

Original title and link: MongoDB with .NET NoRM: Queries (NoSQL databases © myNoSQL)

via: http://codefather.pl/post/1369797147/nosql-no-problem-norm-and-mongodb-tutorial

Juho Mäkinen shares a Cassandra data and access model for a Facebook-like messenger application:

We have built a facebook style “messenger” into our web site which uses cassandra as storage backend. I’m describing the data schema to server as a simple example how cassandra (and nosql in general) can be used in practice.

Make sure you read the post to better understand how data access patterns are important when deciding your data model.

Original title and link: Cassandra: Modeling A Facebook-Style Messenger (NoSQL databases © myNoSQL)

via: http://www.juhonkoti.net/2010/09/25/example-how-to-model-your-data-into-nosql-with-cassandra

Assorted notes from a guy learning MongoDB:

As a good habit, I wrote down the next things I learned and played around with. That is what this blogpost is about, next steps in the learning process of Mongo. This post mainly focussus on Replication Sets, object Identity, WriteConcern and a bit about Sharding.

Original title and link: Learning MongoDB (NoSQL databases © myNoSQL)

via: http://www.gridshore.nl/2010/09/27/still-learning-mongodb/

I hope you like this first sight of the CouchDB database. Couch have many other features, but the documents and views are the central part of the system : once those are well understood, the rest is easily understandable. The most difficult part, as said in the introduction, is to forget years of SQL thinking to build web applications.

Definitely not the first CouchDB and PHP guide — see Quick guide to CouchDB and PHP, CouchDB basics for PHP developers, A not-so-quick guide to CouchDB with PHP — and most probably not the last and/or definitive one.

Original title and link for this post: CouchDB: Getting Started using PHP (published on the NoSQL blog: myNoSQL)

via: http://devzone.zend.com/article/12523

Good intro material about Hadoop (and a bit of Hive):

One design pattern that both Google and Facebook share is the ability to distribute computations among large clusters of machines that all share a common data source. The pattern is called Map/Reduce, and Hadoop is an open source implementation of this. This article is an introduction to Hadoop. Even if you donʼt currently have a massive scaling issue, it can be worthwhile to become familiar with Map/Reduce as a concept, and playing with Hadoop is a good way to do that.

If you are new to map/reduce and Hadoop, keep also in mind that many NoSQL databases — Riak, CouchDB, MongoDB to name a few — are able to run natively map/reduce jobs.

Getting Started with Hadoop originally posted on the NoSQL blog: myNoSQL

via: http://articles.sitepoint.com/article/scale-big-time-with-hadoop

From Basho:

Web applications built with Ruby on Rails have lots of ways to take advantage of scalable, distributed storage systems like Riak. These resources can help you get started.

Video and slides below:

Riak and Rails: 6 Steps for Getting Started originally posted on the NoSQL blog: myNoSQL

via: http://forms.basho.com/riak-and-rails-a-powerful-combination-attended-p

One of the much awaited features in MongoDB 1.6 is replica sets, MongoDB replication solution providing automatic failover and recovery^[1].

Chris Heald has a very detailed guide on setting up MongoDB replica sets:

We’re now up and running with a replica set. We can add new slaves to the replica set, force a new master, take nodes in the cluster down, and all that jazz without impacting your app. You can even set up replica slaves in other data centers for zero-effort offsite backup. If your DB server exploded, you could point your app at the external datacenter’s node and keep running while you replace your local database server. Once your new server is up, just bring it online and re-add its node back into your replica set. Data will be transparently synched back to your local node. Once the sync is complete, you can re-elect your local node as the master, and all is well again.

Update: Kristina Chodorow (10gen) has a 3 part series about MongoDB replica sets: ☞ part 1 (setup), ☞ part 2 (replica sets behind the scene) and ☞ part 3 (migrating live setups to use replica sets).

Quick Guide to MongoDB Replica Sets originally posted on the NoSQL blog: myNoSQL

via: http://www.coffeepowered.net/2010/08/06/setting-up-replica-sets-with-mongodb-1-6/