...
After reviewing the discussions in the mailing lists there seem to be two major usecases that have the need for a Multitenancy support. Although there have some shared requirements, both have a set of special requirements with some complexity to implement that are not so relevant for the other. Of course mixes of both scenarios are possible as well.
| "Virtual Hosting" Scenario |
"Massive Multi Site" Scenario |
![]() Image Modified |
![]() Image Added |
| 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. |
"Massive Multi Site" Scenario
![]()
Image Removed
| 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. |
Usecases
// TODO
