The Advent of Polyglot Persistence in 1905 Hybris for Varying Data Storage Needs

Written by Jeethu Augustine

WCS Senior Lead at Royal Cyber

One of the critical decisions while undergoing a Hybris project is to choose which database to use, and often the decision swings between SQL or NoSQL (Not only SQL). SQL databases are long-established and are viable for most of the times. However, these are unsuited for big data applications. NoSQL databases are preferred for their ease of use, high scalability, and strong resilience.

Polyglot comes to rescue decision-makers. Polyglot Persistence is introduced in Hybris 1905 to provide ease to use different database technologies i.e., RDBMSs, NoSQL, data warehouses, data marts, flat files, content management servers within one business application.

If we wanted to use two different data stores before Hybris 1905 (except for RDBMS / Solr), it would be quite expensive to create a stable version, while with the Hybris 1905 version you can distribute your data application among many data stores.

Besides, this solution allows you to easily configure different data storage units, even at the level of an item in the Hybris system (e.g., shopping cart, customer, inventory, order, etc.). Polyglot Persistence can be used for existing as well for newly created items in the Hybris system. It supports CRUD (create, read, update, and delete) operations along with searching for objects.

The above diagram illustrates a variation in E-Commerce Platform data storage is achieved by blending of RDBMS (typically SQL) with different NoSQL solutions (i.e Key-Value, Document, Graph).

Benefits of using Polyglot Persistence

  • You can store some chunks of data in RDBMS and other chunks in NoSQL.
  • You want to give breathing space to your application while a transaction is being executed. For Instance, the carts in an e-commerce application are highly manipulated data, and they also consist of JOINS with many other database tables to finally show what is visible to the user. If we plan to move it to a database based on flat / JSON files, this could give the system a lot of relief.

Limitations of Polyglot Persistence

  • Data migration between the existing database to the final storage is not supported
  • Data report and audit is not supported
  • Impex import (it requires unsupported FlexibleSearch features such as unions and joins)
  • JOINS, SUBQEUERIES, GROUP BY, CASE, Functions, Operators (LIKE, IN) are not supported

Polyglot persistence integration in Hybris-1905 induces complexity since each data storage solution requires getting familiar with new technology. However, the benefits are worth it because Polyglot persistence results in high performance by processing large volumes of data without slowing down the business application.

Royal Cyber Expertise

Continuing as is with polyglot persistence even when such distributed SQL databases are available means signing up for never-ending development and operational complexity. Royal Cyber SAP Commerce Cloud experts have unsurpassed experience in this platform. Our consultants have the expertise to guide you at every step. For more on this, you can email us at [email protected] or visit

Leave a Reply