tuscany-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Sebastien Delfino <jsdelf...@apache.org>
Subject GSoC NoSQL DataStore scenario, was: [jira] [Commented] (TUSCANY-3522) [GSoC 2011] Develop a 'NoSQL' Datastore component for Apache Cassandra, CouchDB, Hadoop/Hbase
Date Wed, 11 May 2011 04:23:43 GMT
On Sat, Apr 30, 2011 at 12:16 PM, Eranda Sooriyabandara (JIRA)
<dev@tuscany.apache.org> wrote:
>    [ https://issues.apache.org/jira/browse/TUSCANY-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027362#comment-13027362
> Eranda Sooriyabandara commented on TUSCANY-3522:
> ------------------------------------------------
> Here are some works I did up to today,
> 1. Read about SCA
> 2. Setup and checkout some samples of some NoSQL databases,
> In here I used the hector client for Apache Cassandra and couchdb4j (use JSON) client
for Apache CouchDB. I think we can use some of this clients for our implementations. We need
to decide which one to use.
> There are some topics which we need to discuss about as follows,
> Sample scenario which we are going to implement over various databases. In here for which
extent are we going to implement the functionality?
> The REST API. We can discuss about this after finalize the scenario.
> After decide those we can use the database independent parts (REST API) as a SCA component
and mock the database access.

Here are a few ideas of scenarios:

a) a store with a catalog of goods, and a shopping cart app, similar
to the Tuscany store sample;

b) an app allowing you to track the location of your friends, you
build a list of friends, they update their location, and you can query
for the 5 closest ones;

c) a Twitter-like app, you follow a list of people and see the
messages they write.

These three scenarios have pretty different write / read / query
characteristics. We already have REST service examples for (a) in our
store sample. You could just build on that, but if you want more fun,
I think it'd be really interesting to try to come with REST services
for (b) or (c) as well.

Any thoughts from others in the team?

View raw message