Declaration of independence for your IT processes

   agileKubernetesmicroservicessoftware architecture

Microservices map complex IT systems via decoupled processes. Their interfaces are independent of programming languages. Each service stands for a small, sensibly cut task.

An event storming workshop clarifies the service cut

At an event storming workshop we get to know your domain. Together we will work out your domain cut - and get concrete candidates for your microservices. The focus is on professional events; professional and IT experts speak a common language.

Use reasonable cutting criteria

Clear cutting criteria show you how your microservices should be split or merged. Cut primarily according to technical expertise! However, load differences within an API can also suggest cuts, for example.

The Chaos Game: Fake attack for more resilience

In the Chaos Game you introduce errors and attack your microservice landscape: you improve the resilience of your system through fine-grained monitoring and resilience patterns at critical points.

Our visualization tool gives you security

The complexity lies in the communication of the microservices: Our visualization tool MAAT shows the calls during runtime. This way you can check whether the communication relationships are maintained. Frequencies reveal where particularly close links exist and where you have to pay more attention to availability.


The communication of your microservices is complex. System tests are not enough, you have to monitor your microservices. Good observability tools correlate the logs of your microservices. Professional and technical metrics show peak loads and document how well your system is performing.

Your next step begins now

Plan an event storming workshop now and discover the potential of microservices for your domain:

Martin Sturzenhecker, 0151 544 22 083

Would you like to find out more? We're here to help