One thing that comes to mind: we also have to make a decision to use nested containers (possibly better performance for remote services in the VM) or containers next to each other.
-----Original Message----- From: amdatu-developers-bounces at amdatu.org [mailto:[email protected]] On Behalf Of Mark Machielsen Sent: Wednesday, January 05, 2011 8:48 AM To: amdatu-developers at amdatu.org Subject: Re: [Amdatu-developers] Multi-tenancy (and more) design Ok, after all discussion, I want to propose the following: Choice for multitenancy architecture: - by default (and that's what we are going to promote) applications on top of Amdatu are developed as tenantunaware - such bundles are running in a tenant osgi container - when there are good reasons (for example large services, like shindig) a developer can decide to make the service tenant aware - the service will be running in a tenant unaware container and will be offered in the tenant container via remote services (in the service fabric layer) We can however phase the implementation of the multitenancy concept. Proposal for 0.1: - describe the multitenancy concept at the wiki - leave the implementation for multitenancy to the current implementation: no support for tenant unaware services in a tenant container, support for tenantaware services - plan the full multitenancy application in the roadmap - implement the other items for 0.1: - tenantaware useradmin: this is possible with the current implementation we use by adding an adapter (according to Bram) - Cluster support and backup support for Cassandra - JIRA mandatory issues Greetings, Mark. _______________________________________________ Amdatu-developers mailing list Amdatu-developers at amdatu.org http://lists.amdatu.org/mailman/listinfo/amdatu-developers
