[
https://issues.apache.org/jira/browse/GORA-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13942064#comment-13942064
]
Lewis John McGibbney commented on GORA-279:
-------------------------------------------
For my use cases Gora has always acted as a 'broker' of sorts between client
code and some backend persistent store. When we use Gora within a MapReduce
environment we leave the distributed computing to Hadoop.
This is shadowed when we think about data store support. If you use Gora with
Cassandra for example, we would configure a multi node environment on the
Cassandra side however Gora does not need to know about this. You just use the
Gora library and the generated data beans within your client code and forget
about the complexity involved with the DataStore's
> Hazelcast module
> ----------------
>
> Key: GORA-279
> URL: https://issues.apache.org/jira/browse/GORA-279
> Project: Apache Gora
> Issue Type: Wish
> Reporter: Julien Nioche
> Labels: gsoc2014
> Fix For: 0.5
>
> Attachments: gsoc_proposal_draft.odt
>
>
> HazelCast seems to be a popular in-memory data grid
> [http://www.hazelcast.com/]. The community edition is under the ASL v2.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
