Posted by DL on
URL: https://discuss.orbeon.com/Multi-tenancy-tp4655340p4655380.html

I'll have to grapple with this multiple domain issue at some stage (when deploying to cloud) so I guess now is a time to think about it.  

However on first reading the jury still seems to be out on multitenancy architectures.

Was just playing with the thought that if you would assign each tenant an Orbeon "application", you may have a good foundation already.

One problem surely is ensuring security between tenants' databases.

Tenants may not be too happy about sharing their data under the same roof (same database) as other tenants.

Searching for "multiple databases" on eXist forum ..

http://exist.2174344.n4.nabble.com/template/NamlServlet.jtp?macro=search_page&node=2174345&query=multiple+databases

Here is one thread ...

http://exist.2174344.n4.nabble.com/Multiple-physical-database-instances-td2187710.html

and see this request ..

If you make use of more than one eXist-db instance in the same JVM then we would like to hear about it

http://exist.2174344.n4.nabble.com/Request-for-Use-Cases-of-Multiple-eXist-db-instances-in-same-JVM-td3350280.html#a3350433


[EDIT]

And see this nearby thread here on deploying external eXist-DB ...

http://orbeon-forms-ops-users.24843.n4.nabble.com/using-the-xml-db-API-in-XPL-datasource-xml-tp4655360.html

[EDIT again]

My own very early thoughts are to deploy with

tier 1  .. Drupal as front end CMS (multi site / multi domain configuration)
tier 2  .. Orbeon as xforms engine called from Drupal CMS
tier 3  .. eXist multiple databases



[.. and again ]

I found this useful IBM article setting out design options ...

http://www.ibm.com/developerworks/data/library/techarticle/dm-1201dbdesigncloud/

for "DB2" read eXist-DB in our case.