5

Coming from a relational database background, I can make the transition to document oriented databases pretty quickly. Many of the most valuable "relations" are maintained by the hierarchy of the document. Many of the DODB variants of NoSQL also offer a very rich query language as well. This subset of NoSQL I think I understand.

I am looking for a good reference for designing around the database style implemented by Azure Table Storage, S3, and BigTable. It seems like all of the samples I see are trivial implementations.

Do you know of any non-trivial treatments of design in this space?

Dennis Burton
  • 3,282
  • 3
  • 23
  • 30

2 Answers2

1

For Azure Tables specifically (Microsoft's NoSQL database) the following blog post provides some good insight and talks to a couple of patterns to consider http://blogs.msdn.com/b/windowsazurestorage/archive/2012/11/06/windows-azure-storage-client-library-2-0-tables-deep-dive.aspx

Jason Hogg - MSFT
  • 1,369
  • 9
  • 10
0

Oren Eini (alias Ayende Rahien) has written a number of blog posts about designing NoSql databases for RavenDB - his own NoSql implementation.

I guess some of it is specific to RavenDB, but lots would also apply to other NoSql databases.

Geoff Appleford
  • 18,538
  • 4
  • 62
  • 85