Hi Am 01.09.2014 um 01:07 schrieb David Bosschaert <[email protected]>:
> On 30 August 2014 08:36, Felix Meschberger <[email protected]> wrote: >> 2. OSGi Platform services have to be adapted as well. Particularly nasty >> probably are things like SCR and Blueprint which manage objects on behalf of >> bundles and must thus be knowledgeable of that situation maybe also by >> virtue of the MultieTenantActivator and the BundleContext wrappers. > > > Yes, I think in any kind of approach here platform services must be > aware of the multi-tenancy. One of the things that I have been > thinking about is to make OSGi Subsystems fully multi-tenant capable. > It still means that the platform services have to be 'subsystem-aware' > but at least this limits the awareness to one tenant-support API > instead of having to understand many different types of multi-tenant > solutions. Depending on your use case, today's OSGi Subsystems might > already be good enough. Would that mean we would have a subsystem per tenant ? If so, considering we have, say, 50 bundles to be made „multi-tenant-supporting“, it would mean would multiply 50 bundles by X tenants. So for 100 tenants we would have 100 subsystems with a total of 5000 bundles and class loaders ? Can/does that really scale ? I am scared. On the other hand, if tenants have differing sets of bundles, I agree that it might make sense to have subsystems per tenant. But this is another topic of multi tenancy, which involves resource allocation which we cannot handle in standard JVMs yet. Or, I may be completely off track ... Regards Felix > > Best regards, > > David
