Jacques, Pierre and Arum
Thanks for the technical answer.
I agreed with the advantages of a DB per Tenant and the scalability of
the HW infrastructure underneath . Hence the maintenance and support
issues.
I test with v14.12 and advise.
Regards,
Fernando
Le 2015-05-21 03:09, Jacques Le Roux a écrit :
More accurately multi-tenancy has been introduced in trunk in February
2010 and has been continuously improved since.
It works with all the DBMSs you can fiund in the EntityEngine.xml file.
The number of tenants depends on the material resources, not the code.
It's not a solution to scale above thousands tough (you need a DB by
tenant...)
This limitation comes with the obvious advantages of having separated
DBs. You can find details about these advantages on the Net, notably
when it comes to backups things and guarantee access separation...
Jacques
Le 21/05/2015 07:59, Pierre Smits a écrit :
Hi Fernando.
Multi-tenancy has been around since prior r12.x. And is working with
both
PostgreSQL and MySQL.
Best regards,
Pierre Smits
*ORRTIZ.COM <http://www.orrtiz.com>*
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
http://www.orrtiz.com
On Thu, May 21, 2015 at 4:34 AM, FGomez <fgo...@mail.com> wrote:
Hi All,
I wanted to know if anyone has Multi-tenant running in production
(or dev)
with more then 3 tenants/clients with PostgreSql or mySql DBs?
With v13.07 or v14.12 ( I believe the domain on the script is only
available with the 'ant create-tenant' on v14.12 only).
Thanks you for the feedback.
Regards,
Fernando
