Our Microservices Architecture

In addition to a focus on maximum transparency, at E2E Commerce we rely on a agile process model. In our approach, requirements from the specialist area are incorporated in the form of business processes. These business processes are then implemented using process patterns in so-called microservices. Microservices are independent, autonomously running processes on the operating system level, which makes the resulting solution extremely fail-safe. The great advantage of Microservices architecture is that new functionalities and new versions of existing services can be made available quickly and easily several times a day, without interrupting ongoing business.


A Deployment/Roll-Out usually takes 1-2 minutes!

We can distinguish between two types of process patterns:

business integration

Business-Patterns (HOW)

These patterns refer to recurring flow logic. For example, synchronous processing of an order with the online shop and asynchronous forwarding to backend systems such as ERP or CRM.

Advantages: Very fast response to the customer and insensitivity to temporary unavailability of the backend systems.

technical integration

Technical-Patterns (WHAT)

These patterns refer to recurring data logic. For example, the mapping of an order to data structures in a backend system such as CRM.

Separation of process and data logic

Ideally, data logic and process logic can be completely separated in this way, so that changes have only a very limited effect. The resulting solution architecture can be sketched in advance (if all relevant use cases are known), but it can also evolve over time (evolving architecture).

Microservices Architecture – an example

By combining the appropriate microservices, all requirements of the business process are realized (example “Payment Options v1”). In the following example you can also see the change of the architecture from the first to the second iteration.

Connection of a new backend

New requirements of the business process (business process “Payment Options v2” requires the connection of “Backend 2”) can now be implemented quickly and easily. The process does not have to be completely redeveloped. The additional backend system will be connected via a new technical micro service. This in turn is integrated into the process via an extended business microservice and switched “live”.

business process
business process

Complete overview of a sample architecture

e2ecommerce archictecture chance services processes