Integration via UI and Data Replication
However, this approach only tackles the problem on the level of logic integration. Chapter 8 describes another level of integration, namely data replication. This allows a microservice to access comprehensive datasets of a legacy application also with good performance. It is important that the replication does not happen based on the data model of the legacy application. In that case the data model of the legacy application would practically not be changeable anymore since it is also used by the microservice. An integration based on the use of the same database would be even worse. Also at the level of UI integrations are possible. Links in web applications are especially attractive since they cause only few changes in the legacy application.
Content Management Systems
Some examples could be:
- • A microservice can import content from certain sources. Each source can have its own microservice.
- • The functionality that enables a visitor of the web page—for example, to follow an author—can be implemented in a separate microservice. The microservice can either have its own URL and be integrated via links, or it modifies the pages that the CMS delivers.
- • While an author is still known in the CMS, there is other logic that is completely separate from the CMS. This could be vouchers or e-commerce functionalities. Also in this case a microservice can appropriately supplement the system.
Especially in the case of CMS systems, which create static HTML, microservices- based approaches can be useful for dynamic content. The CMS moves into the background and is only necessary for certain content. There is a monolithic deployment of the CMS content, while the microservices can be deployed much more rapidly and in an independent manner. In this context the CMS is like a legacy application.