Community mailing list archives

Re: Can I use Odoo to build a SaaS business apps? Can Odoo support multiple subdomains?

- 04/26/2016 04:31:15
2016-04-26 9:33 GMT+02:00 Ermin Trevisan <>:
> Dominique
>> This is not enough in your case. To use different modules for
>> different customers you need multi-tenant, as already said.
>> For other reasons, you'd rather not run several databases on a single
>> service in production.
> I remember reading a post of yours explaining your approach.
> I do agree that this is not the optimum concerning separation of customers.
> If I remember it correctly, you do offer separate instances with
> separate databases. But in this case, what does multi-tenancy mean, even
> if you are using virtual servers?

The point here is the requirement for different modules. If you put
several databases on a single service, all databases use the same
modules. So my answer.

Now from a generic stand-point, the more separate Odoo services are,
the more secure/stable it is.
Some very demanding instances of mines, run a single database on a
single service on a single virtual server on the customer's dedicated
physical server.
On the other end of the range, like, many customers
use many databases on many services on many virtual servers on many
dedicated servers.
For education, evaluation, test, replay backups, it's OK. For
production, users are invited (but not forced) to use separate
services if they need several databases.

Multi-tenant, aka multi-service, consists in running several Odoo
services on the same server. For instance, a basic virtual server from
SISalp runs three different copies of Odoo called production, taining
and test. Multi-tenancy is a compromise to manage internal training
and updates, but can also be used to save resources for a large number
of services. For example, French University Mooc about ERPs in
november 2015 needed 7000+ simulations for 7000+ students. System was
designed for 10000 capacity, based on 25 virtual servers running 225
Odoo services with 32 databases each.

In SISalp's multi-tenant solution, every service must be isolated in
its own system user, its own home directory and its own postgresql
role. Critical files cannot be read from other users.
If you wish to see it in action for a full virtual server running
several services, all different and independent, you can check and connect with "admin"
password "admin"
This dashboard manages our demo center. You can try and click
everywhere and break everything here ;-).
If you are interested by a single service view (for example Odoo
version 8.0 demo service), connect with "version80" password "admin"

Clouder achieves similar functions but isolates services in Docker
instances whose management is centralized at clouder level, while, at
SISalp, every virtual server is an independent administration unit
managed locally. The aim of SISalp's hosting is to be able to delegate
administration of each virtual server to the user or his local service
provider. I think it is the main point that differentiates the two
approaches, more than old-school/new-school technology.