What are bounded contexts about? As usual, they're about splitting responsibilities to make complex systems simpler and easier manage
The phrase "best practices" is often thrown around in software engineering, serving as a reassuring beacon of correctness. However, in the realm of software architecture, its application is far more nuanced.
There is a conflict here, between the things that need to be done and our time. Our job is to find a way to reconcile this conflict.
The goal is to deliver value to customers as fast as possible while staying in line with business goals and keeping quality at a high level. As we know from experience, fast and high quality usually don't work well together. Let's see what we can do about it.