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

Bram de Kruijff commented on AMDATU-131:
----------------------------------------

0) The core storage functionality should not try to or pretend to be a 
Cassandra! 
1) At this point I see no need for any additional storage engine other then 
out-of-the-box OSGi bundle storage.
2) For a consolidated configurable API/service based backstore mechanism I'd 
say use standard Preferences!

So, IMHO, simple persistent storage is a Preferences service with a bundle 
persistence implementation unless proven inadequate :)


> Marcel said: 
> Like Angelo states in AMDATU-130, each service should have its own 
> abstraction for storage

Sure but I guess we would like to consolidate to one service based 
configurable/selectable/pluggable mechanism at the core/platform level? In my 
suggestion this would be the Preferences service API with some kind of service 
selection mechanism based on registration properties and/or security.

> Ivo said:
>  ... in the real world support engineers just need to have direct access...  
> And that is the reason I added -4-

I agree that, in a real world deployment one would probably want to configure 
some centralized RDBMS (or whatever) backstore for most (but not nenecessarily 
all) data. That does not mean that that implementation should be part of the 
Amdatu core footprint, let alone a web based ui. They key is providing a simple 
implementation, inspectable/debuggable through its service interfaces (and one 
could consider making any kind of UI/REST interface for that outside the core). 
More important is the flexibility to configure any alternative backstore 
implementation and one could never make any sensible generic interface for that 
anyway (due to implementation specifics) so it cannot be part of the core.



> Implement Simple persistent storage for Amdatu core
> ---------------------------------------------------
>
>                 Key: AMDATU-131
>                 URL: http://jira.amdatu.org/jira/browse/AMDATU-131
>             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
>
>
> Some simple storage engine needs to be used to store roles for UserAdmin, 
> configuration for ConfigurationAdmin and tenants for the tenant service. 
> There are a lot of (open source) options, most of them described on this 
> page: http://java-source.net/open-source/database-engines
> The main question however is I think; what do we require from this storage?
> Requirements:
> -1- Very lightweight; small in size, low memory footprint, etc.
> -2- Low software/hardware requirements (i.e. supports Java 1.3)
> -3- The storage engine must be open source and provide a Java API
> -4- A simple web-based GUI would be nice, though not required

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to