Agility through software modularisation

Microservices are easy to understand without explaining the technical complexity behind them. They are used to modularise software and processes. Large projects can be divided into small units and thus be well organised and implemented. That means software can be enhanced and maintained, and individual components exchanged. Microservices make it possible to pursue a best-of-breed approach as early as in the software design phase.

The essential characteristic of microservices is that they can be developed and deployed independently of each other. Each component can use whichever programming language and software architecture works best for its particular use case. Scenarios with different components from different manufacturers, which together form a large software solution, are therefore easy to implement.

Each service is therefore independently responsible for exactly one subtask and is isolated from the outside with regard to its own program logic. Standardised interfaces, such as REST APIs, are used so that the services can communicate with each other. They allow usage data and information to be passed from one component to another via data exchange formats such as JSON or XML without having to know the architecture of the other component.
All the microservices that make up a system can easily run on separate servers or even in separate data centres since the only intersection is the interface. That means that, with proper planning, the solutions cannot only be scaled horizontally but also be made more fail-safe.

There is no universal answer to this question. Instead, you should ask yourself the following questions: What are your specific goals? Why do you want to introduce microservices? What do you want to achieve and improve by their introduction?