Magento, Magento 2

Split Database & Why it is Deprecated

Split Database

The Magento system is highly scalable and includes the ability to use multiple databases at the same time, this feature is called a split database solution. This feature is only available in Magento commerce or now also known as Adobe commerce solutions.

The split database feature was introduced in 2015 by Magento commerce for the merchants who wish to optimize their application on the database level.

        This feature allows component developers to save checkout, order, or product data in separate databases or create a master-slave database model. This separation improves the scalability for accessing the orders, browsing the website, and order management activities.

The ResourceConnections class is responsible for creating a connection between multiple i..e master and slave databases and provides a unified solution. Magento uses CQRS(Command Query Responsibility Segregation) design pattern. This design pattern states that every method should either be a command that performs an action, or a query that returns data to the caller, but not both. This design pattern handles the logic for routing of reading and writing of queries to appropriate databases. The developers don’t need to worry about this.

What are the advantages of setting up multiple databases?

  1. Data backup
  2. Data analysis 
  3. Scalability

Why was the split database feature deprecated?

        The split database feature is deprecated because over the last few years Magento has enhanced its features and merchants now can achieve the same optimization using the single database. Features like elasticsearch. Elastic search used by Magento to save attributes on a document level (features of elasticsearch are out of the scope of the blog) there are many more features like this. This change also allows future enhancement of the Magento platform, Adobe commerce focusing on bringing new microservices-based architecture which will include per business domain storage. This change affords merchants who take advantage of moving to a single database solution the opportunity to reduce complexity, which can in turn help reduce overhead.

Who will be impacted by this?

        After deprecation of split, database features the merchants who are using their on-prem servers or simply who don’t rely on Magento commerce cloud will be affected after this deprecation. Those merchants need to migrate their all databases to a single database

Magento will completely remove this feature in v2.5 but it will not launch till 2022.

Please let me know what do you think about this blog in the comment below, if you want to know more about this topic please write me an email on my mail id

Tagged , , ,

Leave a Reply

Your email address will not be published. Required fields are marked *

The reCAPTCHA verification period has expired. Please reload the page.