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



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

NoSQL Databases in Grails and Spring Data

When checking the ☞ GitHub repository for Grails/GORM entities support for Riak MapReduce I have noticed multiple NoSQL integration projects[1] :

Grails/GORM and NoSQL databases:

  • Gemfire
  • JCR
  • MongoDB
  • Redis
  • Riak

Spring Data and NoSQL databases:

  • AppEngine
  • Cassandra
  • Gemfire
  • JCR
  • MongoDB
  • Redis
  • Riak

What seems to be missing is the Neo4j support in Spring Data, but maybe there’s a different repo for it.

Finally lots of love for NoSQL database in the Java land.

  1. At this time I’m not sure about each of these project status.  ()

Original title and link: NoSQL Databases in Grails and Spring Data (NoSQL databases © myNoSQL)

Grails/GORM Entities Support for Riak MapReduce

Things are becoming clearer to me: Grails/GORM is the Springframework avant-garde experimenting and integrating various NoSQL databases. Early February there were Grails plugins for CouchDB, HBase, Neo4j, and AppEngine, then it was time for Redis support in Grails, followed shortly by MongoDB support in Grails/GORM.

Over the weekend J.Brisbin added support for Riak MapReduce in Grails/GORM. Project on ☞ GitHub.

Spring Data is the emperor’s army “standardizing” the results.

Original title and link: Grails/GORM Entities Support for Riak MapReduce (NoSQL databases © myNoSQL)

Grails/GORM for MongoDB

Our crusade to make GORM ubiquitous across NoSQL stores hit another milestones today as we are pleased to announce GORM for MongoDB.

One of the few times I can say that a Java framework is not playing only catch up with Django or Ruby on Rails.

The plugin is available ☞ here.

The new Grails/GORM for MongoDB plugin is ☞ already welcome:

So, it appears that SpringSource have hidden microphones in our office, and the day we were discussing this issue, they came up with this nice news.

Original title and link: Grails/GORM for MongoDB (NoSQL databases © myNoSQL)


Grails/GORM for Redis Interview

Graeme Rocher (@graemerocher), Grails project lead about Grails support for Redis:

Redis is a key/value store which supports extremely fast read operations so it’s useful in a number of situations where caching solutions have been used, however since Redis supports complex data types like sets, lists and hashes you can also do some more advanced querying compared to other key/value stores. This makes it appropriate for a range of scenarios from sorting data, calculating statistics, queueing jobs or just basic caching. As an example Redis’ set type allows you to store a unique set of values and easily return random entries or pop (remove) entries from a set. Implementing this type of functionality in a performant way on a relational database is typically much harder.

Even if compared with a caching solution, Redis will actually persist your data.

Original title and link for this post: Grails/GORM for Redis Interview (published on the NoSQL blog: myNoSQL)


Redis: Support in Grails Reaches Milestone 1

In February, while reviewing Grails support for NoSQL databases, I’ve listed CouchDB, HBase, Neo4j, and Google AppEngine. But siince then, many things have changed. Redis is now under VMWare’s umbrella too, so today’s announcement of adding support for Redis in Grails should not be a surprise:

What is GORM for Redis? Quite simply it allows Grails developers used to the convenience of features such as dynamic finders, criteria and named queries to take advantage of Redis as their underlying store instead of Hibernate.

In case you are wondering how mapping objects to Redis happens, Graeme Rocher (@graemerocher), Grails project lead, replied:

@al3xandru hashes for entities, sets for associations and indices, set operations for querying. Simple really :-)


Original title and link for this post: Redis: Support in Grails Reaches Milestone 1 (published on the NoSQL blog: myNoSQL)