[
http://jira.amdatu.org/jira/browse/AMDATU-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bram de Kruijff closed AMDATU-130.
----------------------------------
Assignee: Ivo Ladage - van Doorn (was: Bram de Kruijff)
Closed for 0.0.6
> 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: Amdatu 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
