A list of DynamoDB libraries covering quite a few popular languages and frameworks:

A couple of things I’ve noticed (and that could be helpful to other NoSQL database companies):

1. Amazon provides official libraries for a couple of major programming languages (Java, .NET, PHP, Ruby)
2. Amazon is not shy to promote libraries that are not official, but established themselves as good libraries (e.g. Python’s Boto)
3. The list doesn’t seem to include anything for C and Objective C (Objective C is the language of iOS and Mac apps)
   

Original title and link: DynamoDB Libraries, Mappers, and Mock Implementations (NoSQL database©myNoSQL)

via: http://aws.typepad.com/aws/2012/04/amazon-dynamodb-libraries-mappers-and-mock-implementations-galore.html

The usual getting started guide for .NET developers:

The object persistence functionality in the AWS SDK for .NET enables you to easily map .NET classes to Amazon DynamoDB items. By using your own classes to store and retrieve Amazon DynamoDB data, you can use Amazon DynamoDB without worrying about data conversion or developing middle-layer solutions that interface with the Amazon DynamoDB service.

Original title and link: DynamoDB Tutorial for .NET: Using Amazon DynamoDB Object Persistence Framework (NoSQL database©myNoSQL)

via: http://aws.amazon.com/articles/2790257258340776

The traffic of our football news syndicating website (Kick News) has been steadily growing a lot since it launched. When we redeveloped it a couple of years ago, we used an in-process cache, by creating an IQueryable extension method that uses an md5 hash of the underlying SQL query as the key. This worked reasonably well, but has it’s obvious problems, such as the caches needing to be refilled when the app pool recycles or when the server is restarted. On our busy site, this means we had to wait until the caches are full before we serve any requests or it would overload our database server, which is unacceptable. Before the site gets any busier we’re going to move to an out-of-process cache and the are 3 main options we’ve considered are Redis, Memcached and Windows Server AppFabric 

From these 3 solutions, only Redis will help address the cache warm-up issue.

Original title and link: Cache Warm-Up: Redis vs Memcached vs Microsoft AppFabric (NoSQL database©myNoSQL)

via: http://www.ichi.co.uk/post/18280190946/microsoft-appfabric-vs-redis-windows-port

This tutorial is meant for the .NET developers to get started with Amazon DynamoDB. I will show you how to create a Table and perform CRUD operations on it. Amazon DynamoDB provides a low-level API and an Object Persistence API for the .NET developers. In this tutorial, we will see how to use the Object Persistence API to talk to Amazon DynamoDB. We will model a component that represents a DVD Library with capabilities to add, modify, query and delete individual DVDs.

Looks like a lot of code just to demo some CRUD operations.

Original title and link: Step-by-Step Guide to Amazon DynamoDB for .NET Developers (NoSQL database©myNoSQL)

via: http://cloudstory.in/2012/02/step-by-step-guide-to-amazon-dynamodb-for-net-developers/

Marcin Budny:

CouchDB seems to be a solid piece of software used by really big players and what’s more – it’s free. It’s well developed community guarantees that you will get the support and tools you need to build your great apps. Yet, lack of transaction support will make your life harder.

Original title and link: CouchDB Through the Eyes of a .NET Developer (NoSQL database©myNoSQL)

via: http://marcinbudny.blogspot.com/2011/10/few-thoughts-on-couchdb.html

Niklas Lundberg summarizes the advantages of using the native .NET document database RavenDB:

As a .NET developer the document database RavenDB is attractive since it provides us with a built-in .NET API, HTTP API and many of the features a NoSQL database can offer. In a web environment the HTTP API is useful because it could eliminate the need for a middle tier for simple scenarios where you don’t need all the features the server side could offer. In RavenDB all documents are stored as JSON and its input and output is also JSON.

And under the covers, RavenDB has a couple more niceties:

• RavenDB bundles: replication, versioning, authorization, spatial queries
• Multi-Document Transactions in RavenDB vs Other NoSQL Databases
• RavenDB and attachments
• RavenDB Filtered Replication
• RavenDB and HTTP Caching
• RavenDB to add auto sharding

Original title and link: Why RavenDB for .NET Development? (NoSQL database©myNoSQL)

via: http://blog.jayway.com/2011/09/22/nosql-with-ravendb/

Anyway, CouchDB is still quite young, and hasn’t seen a lot of attention outside the Ruby and Python communities. This sucks. I would like to see a well-designed open-source library for .NET applications using CouchDB for persistence. Here are some features such a library might provide over and above raw HTTP WebRequests:

• Generics and automatic serialization/deserialization of .NET objects
• mapping RESTful HTTP error codes to .NET exceptions
• Implicit Offline Optimistic Lock via document revisions
• LINQ expressions for Map/Reduce functions
• ID generators like NHibernate

Remember what I was saying about CouchDB official libraries? Even if there’s an official list of drivers, that’s not enough.

Original title and link: Wanted: A kickass .NET API for CouchDB (NoSQL databases © myNoSQL)

via: http://richarddingwall.name/2009/05/02/wanted-a-kickass-net-api-for-couchdb/

The “hello world” for web applications is a basic blog with posts and comments. This time using MongoDB and C# MVC 2.0:

First things first, call this a disclaimer if you like…. This blog is what I took from working with MongoDB and MVC C#. I have worked with C# .Net with web forms but never MVC or MongoDB. This is basically my experience setting up and creating an application to create a blog with posts and comments. I’ll start by giving a brief description, in layman’s terms, as to what MVC is all about.

Beginners Guide to MongoDB and C# MVC 2.0 originally posted on the NoSQL blog: myNoSQL

via: http://www.dotnetconvo.com/post/view/2010/8/3/exploring-mongodb-and-an-n-tier-mvc-2-0-architecture-using-c