Hi Mark, I wonder what would be the approach for Amdatu services themselves; should we make them tenant aware as much as possible or not? I'm not sure if we should promote tenant unaware services either. Both tenant aware/unaware service have their pros and cons:
Tenant aware services - More flexible, can be hosted by a single-tenant as well as a multi-tenant container - No real isolation (unless they run on a single-tenant container) Tenant unaware services - Less flexible, must be deployed onto a single-tenant container - Easier to implement, though I hardly think this is an argument. Making a service tenant aware is really not that hard. - Better isolation (though that is not a quality of the service itself but of the fact that it forces you to run it in a isolated container) - Worse for resource consumption, as they must be distributed among all containers So in fact, tenant aware services have all the benefits of a tenant unaware service, when they are deployed on a single-tenant container (just like the tenant unaware services). The only argument for making services tenant unaware would be that is just a bit easier to implement. So why would we promote implementing services tenant unaware? Regards, Ivo -----Original Message----- From: amdatu-developers-bounces at amdatu.org [mailto:[email protected]] On Behalf Of Mark Machielsen Sent: woensdag 5 januari 2011 11:25 To: amdatu-developers at amdatu.org Subject: Re: [Amdatu-developers] Multi-tenancy (and more) design Marcel wrote: "I am not sure what you intend to say here. Can you clarify this a bit? Are you proposing not to implement the the proposal above for 0.1?" Correct. It seems that it takes quite some time to implement this (including the remote services). My proposal is to release 0.1.0 at short notice (to serve BC and Luminis), to describe the solution (which probably needs some discussions) and plan in the roadmap. Greetings, Mark. -----Original Message----- From: amdatu-developers-bounces at amdatu.org [mailto:[email protected]] On Behalf Of Marcel Offermans Sent: Wednesday, January 05, 2011 9:59 AM To: amdatu-developers at amdatu.org Subject: Re: [Amdatu-developers] Multi-tenancy (and more) design On 5 Jan 2011, at 8:48 , Mark Machielsen wrote: > 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) Agreed. > We can however phase the implementation of the multitenancy concept. > > Proposal for 0.1: > - describe the multitenancy concept at the wiki Ok. > - leave the implementation for multitenancy to the current implementation: no > support for tenant unaware services in a tenant container, support for > tenantaware services I am not sure what you intend to say here. Can you clarify this a bit? Are you proposing not to implement the the proposal above for 0.1? > - plan the full multitenancy application in the roadmap Fair enough, if we all agree on the proposal above, we can start working towards it. > - 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) Probably, but why not simply deploy a default User Admin implementation in each tenant container? > - Cluster support and backup support for Cassandra Sounds like a big one! > - JIRA mandatory issues Did we already tag those? Greetings, Marcel _______________________________________________ Amdatu-developers mailing list Amdatu-developers at amdatu.org http://lists.amdatu.org/mailman/listinfo/amdatu-developers _______________________________________________ Amdatu-developers mailing list Amdatu-developers at amdatu.org http://lists.amdatu.org/mailman/listinfo/amdatu-developers
