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

--
View this message in context: http://orbeon-forms-ops-users.24843.n4.nabble.com/Multi-tenancy-tp4655340p4655380.html
Sent from the Orbeon Forms (ops-users) mailing list archive at Nabble.com.


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws