The more I think about it, the more I like the idea of a setup
running each operation on its own DB. Maybe based on Serpent's
DB-Synchronization module it could be possible to develop a more
and more sophisticated cross-DB consolidation, which would solve
the multi-website issue by eliminating it.

On 02.05.2017 09:11, Jos De Graeve
wrote:

Hello Ermin,

Doing a multi-website setup is quite tricky. If you want
to proceed with that option, you will need to assess if that
is the right solution for you.

The advantage of a multi-website solution is that it runs
on a single DB. So if the maintenance of this DB is heavy (
creating / updating products, prices, customer records etc,
reporting requirements ) then you might consider a
multi-website odoo DB.

With multi-website there are a lot of constraints:

* it is not very stable ( i have seen strange issues with
it on v10 ) - pages appearing on the wrong website etc.

* very hard to have each website its own theme ( ie- not
possible without customization )

* website modules are not multi-website aware. A lot of
these issues can be solved with multi-company access rules,
but that is not very easy.