svn commit: r914671 - in /websites/staging/gora/trunk/content: ./ about.html

[bu...@apache.org]

Author: buildbot
Date: Tue Jul  1 21:34:28 2014
New Revision: 914671

Log:
Staging update by buildbot for gora

Modified:
    websites/staging/gora/trunk/content/   (props changed)
    websites/staging/gora/trunk/content/about.html

Propchange: websites/staging/gora/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Jul  1 21:34:28 2014
@@ -1 +1 @@
-1607191
+1607198

Modified: websites/staging/gora/trunk/content/about.html
==============================================================================
--- websites/staging/gora/trunk/content/about.html (original)
+++ websites/staging/gora/trunk/content/about.html Tue Jul  1 21:34:28 2014
@@ -156,10 +156,10 @@ under the License. 
   <div class="container" id="Gora_About Apache Gora&amp;trade;">
 
 <h2 id="why-gora">Why Gora?</h2>
-<p>Although there are various excellent ORM frameworks for relational databases, data modeling in 
+<p>Although there are various excellent ORM frameworks such as JPA, Apache OpenJPA, Hibernate, etc 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. Gora fills this gap by giving the user an easy-to-use in-memory 
+of the data models in column stores (for example). Gora fills this gap by giving the user an easy-to-use in-memory 
 data model and persistence for big data framework with data store specific mappings and built 
 in <a href="http://hadoop.apache.org">Apache Hadoop&trade;</a> support.</p>
 <p>The overall goal for Gora is to become the standard data representation and persistence framework 
@@ -189,14 +189,18 @@ for big data. The roadmap of Gora can be
 <li><b>Development and/or Testing Engineers</b> looking to quickly set up and deploy applications on top of
   Big Data storage mediums. This includes testing how applications are suited to underlying data stores
   as data stores are easily interchanged. </li>
-<li>Developers interested in <b>technology agnostic storage methods</a> for addressing data storage tasks.</li>
+<li>Developers interested in <b>technology agnostic storage methods</b> for addressing data storage tasks.</li>
 <li><b>Decision Makers</b> looking to implement a flexible storage framework under the <a href="http://www.apache.org/licenses/LICENSE-2.0">most liberal
   open source license available</a>.</li>
 </ul>
 <h2 id="background">Background</h2>
 <p><b>ORM</b> stands for <a href="http://en.wikipedia.org/wiki/Object-relational_mapping">Object Relation Mapping</a>. It is a technology which abstacts the persistency layer 
 (mostly Relational Databases) so that plain domain level objects can be used, without the cumbersome 
-effort to save/load the data to and from the database. Gora differs from current solutions in that:</p>
+effort to save/load the data to and from the database. </p>
+<p>Gora extends this concept to introduce <b>Object-to-Datastore Mapping</b> where the underlying 
+technological implementations rely mostly on non-relational data modeling. In essence
+Gora provides storage abstraction for NoSQL technologies.</p>
+<p>Gora differs from current solutions in that:</p>
 <ul>
 <li>Gora is specially focussed at NoSQL data stores, but also has limited support for SQL databases.</li>
 <li>The main use case for Gora is to access/analyze big data using <a href="http://hadoop.apache.org">Apache Hadoop&trade;</a>.</li>