u/Hot_Code5129

Hi,

I’m writing a blog post about Strategic DDD and finding subdomains.

I already found some heuristics, for example:

- words with different meaning in different teams

- things that change together

- important business events

- who owns the data / source of truth

- rules that must be consistent

- parts of process or user journey

- things reused by many products or processes

But I’m curious how people do this in real projects.

What heuristics do you use to find subdomains or bounded contexts?

How do you check later if the split was good?

Do you have some examples where the first split was wrong?

I’m not looking for perfect theory, more practical experience.

Thanks!

Do you see Transactional annotation as the default solution for almost everything, or have you encountered cases where explicit transaction boundaries worked better?

What about WebFlux/R2DBC applications? Is Transactional still a natural approach there, or teams more often use explicit transaction management with TransactionalOperator?

I’m asking because I was exploring this topic and trying to contribute something back to Java community. When working with reactive applications, I started to wonder if transaction boundaries should be more visible in the application workflow instead of being hidden behind annotations.

Maybe I’m overthinking this, but I would be interested to hear opinions from people who run Spring applications in production.