[ 
http://jira.amdatu.org/jira/browse/AMDATU-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10145#action_10145
 ] 

Angelo van der Sijpt commented on AMDATU-130:
---------------------------------------------

I like the term SSE :) It does, however, deserve its own issue, which we can 
use to flesh out the interface.

For the non-core bundles, they still should not rely on Cassandra, unless they 
are sure they will _only_ be used in combination with Cassandra. So, the 
Shindig and Profile service should have their own abstraction for storage, for 
which we can supply a SSE-based implementation.

The courses services, I'm not so sure. It is an example service, after all, it 
all depends on whether we feel like supporting it until kingdom come.

> Replace Cassandra and Bundle cache storages for Amdatu core with some simple 
> persistent storage
> -----------------------------------------------------------------------------------------------
>
>                 Key: AMDATU-130
>                 URL: http://jira.amdatu.org/jira/browse/AMDATU-130
>             Project: Amdatu
>          Issue Type: Task
>          Components: Platform - Persistence
>    Affects Versions: 0.0.6
>            Reporter: Ivo Ladage - van Doorn
>            Assignee: Ivo Ladage - van Doorn
>             Fix For: 0.0.6
>
>
> Services that are considered to be part of the "Amdatu Core" should not rely 
> on the availability of some sophisticated storage like Cassandra. Currently 
> this is the case, for example the UserAdmin store depends on Cassandra. No 
> choice on what storage engine should be used has been made yet. However, say 
> we choose for the storage engine "SSE" (SimpleStorageEngine). Then the 
> following changes are necessary:
> - Add a UserAdmin storage implementation for SSE. Note that the cassandra 
> implementation will be moved to the cassandra subproject.
> - The Tenant service should store Tenants by default in SSE. The cassandra 
> implementation will be moved to the cassandra subproject.
> - Implement a ConfigurationAdmin that persists using SSE (currently it 
> persist in the bundle cache)
> Furthermore, maybe the following non-core components should be updated too:
> - The Shindig opensocial container and gadget management service should store 
> all info (i.e. Gadgets, AppData) in SSE. What to do withe the cassandra 
> implementation?
> - Same for the profile service
> - The course service example should also provide an example for SSE storage

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.amdatu.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to