...
Table of Contents | ||
---|---|---|
|
Multitenancy Status Quo (
...
October 2014)
Resources and discussion on MultiTenancy in Sling from the last months:
- Current implementation of Sling Tenant: http://svn.apache.org/repos/asf/sling/trunk/contrib/extensions/tenant (no documentation available besides the source code currently)
- Other Wiki pages:
- Multitenancy Support (First draft Felix Meschberger from 2009)
- Multitenancy Support Integration (proposal from Andreas Schaefer from February 2014)
- Context-specific configuration use cases
- Ideas for a multi-tenant and multi-module content model
- Recent discussions in the Mailing list:
- Proposal from Andreas Schaefer (February 2014): http://apache-sling.73963.n3.nabble.com/Tenant-Implementation-in-Sling-td4031217.html
- RT from Carsten Ziegeler (August 2014): http://apache-sling.73963.n3.nabble.com/RT-Multi-Tenancy-td4037558.html
- RT from Bertrand Delacretaz (August 2104): http://apache-sling.73963.n3.nabble.com/RT-The-various-roles-of-multitenant-content-td4037819.html
- Proposal from Stefan Seifert (October 2014)Proposal from Andreas Schaefer: http://apache-sling.73963.n3.nabble.com/Tenant-Implementation-in-Sling-td4031217PROPOSAL-Context-specific-configuration-for-Apache-Sling-Multitenancy-td4041134.html
- RT from Bertrand Delacretaz (January 2015): http://apache-sling.73963.n3.nabble.com/RT-Ideas-for-a-multi-tenant-and-multi-module-content-model-tt4046683.html
Definition of terms
Definition of terms used in this wiki page
...
"Virtual Hosting" Scenario | "Massive Multi Site" Scenario |
---|---|
In this scenario Sling is used for "virtual hosting", that means hosting multiple tenants that should be fully isolated. The main goal according to the wikipedia definition is cost saving, that means instead of a single sling instance and the corresponding infrastructure for each tenant all tenants are hosted in a shared instance. There is no need for content sharing. Usually the users of each tenant are distinct from each other. | In this scenario the whole instance is used by one corporation which has the need to host a huge number of sites (e.g. 100 or 1,000 or more sites) in a single instance. Besides cost saving of having a single instance, additional goals are the support of content sharing. Although there are some users that have only access to a single site, there are plenty of users that can have access to multiple sites (read/write or only read). To structure the huge number of sites a hierarchy of regions and subregions is used. |
Use cases / requirements
Topic/Scenario | "Virtual Hosting" Scenario | "Massive Multi Site" Scenario |
---|---|---|
Tenant definition |
|
|
Content |
|
|
i18n |
|
|
Scripts |
|
|
Bundles |
|
|
Security |
|
|
Configuration |
|
|