
Repository Pattern Spring Data Overlap Explained Clearly
Compare the repository pattern with Spring Data repositories: what each is for, when a domain interface over Spring Data helps and when it adds nothing.
Layers, modules, boundaries and the decisions that are cheap now and expensive in two years.

Compare the repository pattern with Spring Data repositories: what each is for, when a domain interface over Spring Data helps and when it adds nothing.

Compare an anemic domain model with a rich one in Java: where the rules live, an order example in both styles, tests, persistence and a practical way to move.

Write a Spring Boot starter in two modules: an auto configuration with properties and conditions, and a thin starter that pulls it in with its dependencies.

Organise Java packages by feature instead of by layer: a layout for Spring Boot, package private visibility, shared code rules and a path to modules.

Compare microservices and a monolith by team size, deployment, data and operations, and see why a modular monolith is the right starting point for most.

Model money, time ranges and identifiers as value objects in Java with records, validation in the constructor, immutability and equality by value.

Structure a Spring Boot app into modules, verify the boundaries in a test, communicate through events and test one module at a time with Spring Modulith.
We send one email when a new post is published. No spam.