Database partitioning with virtual instances and objects https://liferay.dev/c/message_boards/find_thread?p_l_id=119785294&threadId=123076402 2026-04-03T17:43:46Z 2026-04-03T17:43:46Z Jamie Sammons https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&messageId=123084308 2024-11-19T16:39:31Z 2024-11-19T16:39:30Z

<p>Feature Request Created: https://liferay.atlassian.net/browse/LPD-42487</p>

Jamie Sammons 2024-11-19T16:39:30Z Jonas Wanner https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&messageId=123076401 2024-11-19T16:30:02Z 2024-11-15T10:29:28Z

<p>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.</p> <p>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.</p> <p>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.</p>

Jonas Wanner 2024-11-15T10:29:28Z