Hi, On Fri, Jul 25, 2014 at 8:04 AM, anjan <[email protected]> wrote: > ...we do not want to share the repositories (Data store, Version > store) across the tenants... > ...Any alternative > solution to support multiple tenants?...
If you're not sharing the content repository between tenants, what do you want to share between them? It looks like you could simply use one Sling instance per tenant, and if they are sharing code you can embed that in OSGi bundles (including scripts, using the bundle resource provider) to help with version management. Sling itself doesn't need lots of heap memory to operate, so these individual instances can be quite lean. If you need heavier processing, I would delegate that to separate worker instances, coordinated with a message bus for worker load balancing. -Bertrand
