Ilkka Seppälä

The simple single module usage is documented in `README.md` but what are the configuration options for multimodule builds? There is one example at https://github.com/iluwatar/java-design-patterns/blob/master/aggregator-microservices/pom.xml

When urm-maven-plugin is added to pom.xml Eclipse fails to use it in the build.  Workaround is to disable the plugin in the Eclipse build and use it only in...

https://microservices.io/patterns/testing/consumer-side-contract-test.html

Microservice pattern: Consumer-driven contract test

1

**Description:** The Microservices - Service Integration Contract Test design pattern ensures that microservices can communicate and function together as expected. This pattern involves creating and maintaining contract tests that verify...

Microservice pattern: Service component test

1

**Description:** The Service Component Test design pattern is essential for validating the behavior and functionality of individual microservices within a microservice architecture. This pattern ensures that each service component is...

Service-Oriented Architecture pattern

2

Introduce the Service-Oriented Architecture (SOA) pattern to enhance modular service interaction. Service-Oriented Architecture (SOA) is a design pattern where services are provided to other components by application components, through a...

Refactor Layered Architecture pattern

1

A couple of specific refactorings are needed for Layered Architecture code example. - Runner.java has no main entry point and can't be executed in the IDE. Let's add this. -...

**Description:** The Microservices - Transaction Log Tailing design pattern focuses on maintaining a consistent and up-to-date data view across different microservices by tailing the transaction log of a database. This...

**Description:** The Transactional Outbox design pattern ensures reliable communication between microservices by storing messages in an outbox table as part of the same local transaction that modifies application data. This...