DevOps is about communication and responsibility. A great product is the result of great cooperation.

Do you really need a cluster of pods, service mesh, and stream-processing platform right now?

It is unfortunate that monolith has become a dirty word. In fact, a physical monolith is typically the right thing to do. Pure evil is monolithic thinking.

How do Java Records fit to the object-oriented design?

Interfaces are good stuff. Does that mean the more the better?

Configuration is part of the application API, so the same rules apply to it: no leak of implementation detail.

Defining service boundaries is hard. Let's bring some colors and make it fun!

Which purpose has a Repository? To which layer does it belong to? And how to implement it correctly?

Collection, List and Set are terms very familiar to developers but hardly used by business experts. Therefore, they should not be part of the domain (API).

There are situations where events and commands seem to be a good solution for a problem. Where to use events and where are commands the best fit?