We recently faced a use case where we wanted to utilize the Liferay
instances feature in combination with objects. The use case was like a
multi tenancy white label product, where companies could buy a license
and use the platform for their customers. Every company would then
have its own virtual instance.
As we initially planned the product architecture like this, we
quickly faced the problem that for security and data privacy reasons,
we don't want to have the data in the same database for all our
customers. We would want to have a separate database for every
instance. This was possible in Liferay 6.2 with database sharding but
has since been removed.
(https://learn.liferay.com/w/dxp/installation-and-upgrades/upgrading-liferay/other-upgrade-scenarios/upgrading-a-sharded-environment).
With the objects, it would also be very useful to be able to define a
database, where the object should be stored.
According to this fast track article, Liferay internally uses such a
database partitioning feature (possibly for its SaaS product) and it
would be very helpful if Liferay would provide this to us as Liferay
developer / architects as well.
