Open source in-memory data model and persistence for big data framework Apache Gora™ version 0.3, was released in May 2013. The 0.3 release offers significant improvements and changes to a number of modules including a number of bug fixes. However, what may be of significant interest to the DynamoDB community will be the addition of a gora-dynamodb datastore for mapping and persisting objects to Amazon's DynamoDB. Additionally the release includes various improvements to the gora-core and gora-cassandra modules as well as a new Web Services API implementation which enables users to extend Gora to any cloud storage platform of their choice.
This 2-part post provides commentary on all of the above and a whole lot more, expanding to cover where Gora fits in within the NoSQL and Big Data space, the development challenges and features which have been baked into Gora 0.3 and finally what we have on the road map for the 0.4 development drive.
Introducing Apache Gora
Although there are various excellent ORM frameworks for relational databases, data modeling in NoSQL data stores differ profoundly from their relational cousins. Moreover, data-model agnostic frameworks such as JDO are not sufficient for use cases, where one needs to use the full power of the data models in column stores for example. Gora fills this gap by providing an easy-to-use in-memory data model and persistence for big data framework with data store specific mappings and built in Apache Hadoop™ support.
The overall goal for Gora is to become the standard data representation and persistence framework for big data. From a development point of view, this challenge however comes in many shapes and sizes and in many flavors, some of which we discuss shortly. For the time being however lets consider the following (founding) goals for Gora as a top level project within the Apache Software Foundation. Gora aims to provide:
· Data Persistence : Persisting objects to Column stores such as Apache HBase™, Apache Cassandra™, Hypertable; key-value stores such as Voldemort, Redis, etc; SQL databases, such as MySQL, HSQLDB, flat files in local file system of Hadoop HDFS;
· Data Access : An easy to use Java-friendly common API for accessing the data regardless of its location;
· Indexing : Persisting objects to Apache Lucene and Apache Solr indexes, accessing/querying the data with Gora API;
· Analysis : Accesing the data and making analysis through adapters for Apache Pig, Apache Hive and Cascading;
· MapReduce support : Out-of-the-box and extensive MapReduce (Apache Hadoop™) support for data in the data store.
In terms of where the Gora community is relative to the above, there are currently data store implementations for the distributed key/value store Apache Accumulo, data serialization system Apache Avro, column family data store Cassandra, distributed big data store HBase, the HDFS and now Amazon's DynamoDB.
One underlying formality which has come apparent when attempting to provide a common persistence layer for all of the above data stores (and more), is that the NoSQL and Big Data communities are moving extremely quickly. As expected, communities and consequently code bases also move in myriad of directions meaning that an overwhelming practical hurdle involves keeping up with the rush. The NoSQL space in particular is young and has such experienced astronomical growth in recent years with the best open source products being the ones which have ridden the wave. It is however important to consider that the NoSQL storage abstraction space is even younger, consequently Gora (being the leading open source ASLv2 licensed NoSQL storage abstraction product) is evolving in parallel. By nature the Gora community is diverse in its entirety and the product reflects this entirely. In the second part of this post we provide somewhat of a deep dive covering both the goodies and the technical challenges we encountered during the development of Gora 0.3.
2nd part of the post:
About the Authors:
Renato Marroquin is a Computer Science Master by the Pontifical University of Rio de Janeiro with the thesis titled "Experimental Statistical Analysis of MapReduce Jobs". He is currently a Computer Science Professor at Universidad Catolica San Pablo in
Lewis John McGibbney holds his PhD in Legislative Informatics from