← Graph

Risk of misidentifying domains during legacy re-architecture

question 2 connections

Audience member notes that the worst cost of modularisation — especially with microservices — is misidentifying domains. Krzywda agrees: he once worked on a project that jumped straight to microservices certain of the domains and got the split badly wrong; they merged services back into a monolith and re-modularised. Don't modularise too early with aggressive techniques. But typical domains (pricing, payments) are safe: if you have price, you have pricing — those boundaries are reliable.

answer_summary
Yes, it's a real trap — early aggressive modularisation (microservices, engines) around guessed domains is dangerous. Typical domains are safe starting points; start broad and refine later.
question Risk of misidentifying domains during legacy re-architecture
about
Bounded Context concept
Concerns how to draw domain boundaries correctly.
question Risk of misidentifying domains during legacy re-architecture
asked_at
Asked during Q&A.

Provenance

Read by
10 extractions