adesso Blog

Microservices are a prevailing trend in software architecture that breaks down large systems into independent units. They offer advantages, but are not always necessary. Alternatively, a modularised monolith can be useful, especially if the boundaries between microservices are fluid. In this blog post, I will discuss modularisation concepts in the Java ecosystem, with a focus on Spring Modulith.

Services have to inform each other about important business events, such as price changes or order events, in microservice architectures. These integration events are transmitted using methods such as message queues or HTTP POST requests. Guaranteeing consistency is critical to ensuring that events are only dispatched if the business logic in the sending service is successfully completed. The ‘event store’, which was inspired by Vaughn Vernon, does just that. In my blog post, I describe an implementation scenario involving Java using Spring and Spring Data JPA, where Spring application events play a different role than integration events.

You need to consider a number of things to successfully implement a microservice architecture, including questions like: How do we deal with transactionality? How should the system respond if an error occurs in the middle of a distributed business process? This blog post provides answers to these questions.

Microservices have many advantages. But the monitoring and maintenance of complex microservice architectures are time-consuming. The so-called service mesh can provide a remedy. Stephan Wies explains in this article how this works and what advantages and disadvantages it offers.