Cloud native microservices
A-TO-MIC transformation
A-TO-MIC is a software tool to support the migration of legacy applications to the cloud. For benefiting of the great advantages that cloud applications offer, the legacy application has to be transformed from a non-scaling monolithic application to a highly scalable distributed microservice architecture, that fits best to the cloud suppliers of our days.
What is A-TO-MIC and how does it work?
From global schema to local schemas
A-TO-MIC Goal
The goal of the A-TO-MIC principle is the creation of a microservice architecture from a non-scalable monolithic legacy application on the basis of the ER-Database model of the legacy application..
A-TO-MIC Starting Point
At the beginning of the transformation, there is a relational data model that is represented as a SQL-DDL script. This can be the schema of a legacy application or a new schema designed by a modeling tool for creating database schemas.
A-TO-MIC Endpoint
At the end of the transformation work, there will be the blueprint for a microservice architecture. The monolith has been split up into 7 microservices. Each of the microservices has its own local database schema. The different local databases are synchronized with the help of a message broker. The logical dataflow between the microservices is shown in the last graph.
A-TO-MIC Result
The result of the architecture transformation can be discussed within the system decomposition matrix. The matrix is an indicator for the effort that a migration to a microservice architecture will cost.
Scalability
Mathematical Transformation
Based on the modeling of the user A-TO-MIC calculates the distributed local schemas and the hosting microservices. You can think of it like a human worker that can only make the work of two hands. If 18 hands would be needed for the work, in the monolithic picture, eight additional people would have to be hired. In the microservice picture, the one worker would just increase the amount of his hands from two to 18. This is just an example to show the scalability of the microservice architecture, where a human could have 13 brains or 18 hands or 22 feet. This would only depend on what the person is doing: thinking about the world, building a house with the own hands or playing football. But please do not do that with a real person.
