In-Memory Data Grids - what and why's

The need

As we discussed previously , data storage need increases exponentially . We need more and more place to hold more and more data. We want it to be high available, scalable and super fast.  Here is where In Memory data grids come into the picture .

The model

The data model is distributed across many servers in a single location or across multiple locations.  This distribution is known as a data fabric.  This distributed model is known as a ‘shared nothing’ architecture.

• All servers can be active in each site.
• All data is stored in the RAM of the servers.
• Servers can be added or removed non-disruptively, to increase the amount of RAM available.
• The data model is non-relational and is object-based. 
• Distributed applications written on the .NET and Java application platforms are supported.
• The data fabric is resilient, allowing non-disruptive automated detection and recovery of a single server or multiple servers.

Starting point

• VMware Gemfire                                                 (Java)
• Oracle Coherence                                             (Java)
• Alachisoft NCache                                              (.Net)
• Gigaspaces XAP Elastic Caching Edition            (Java)
• Hazelcast                                                           (Java)
• Scaleout StateServer                                          (.Net)

• IBM eXtreme Scale
• Terracotta Enterprise Suite
• Jboss (Redhat) Infinispan

Links
http://www.infoq.com/articles/in-memory-data-grids