Too Long; Didn't Read
I’m really amused that <a href="https://softwareengineering.stackexchange.com" target="_blank">softwareengineering.stackexchange.com</a> has only <a href="https://softwareengineering.stackexchange.com/questions/316819/how-to-clearly-define-boundaries-of-a-bounded-context" target="_blank">two</a> <a href="https://softwareengineering.stackexchange.com/questions/328320/how-to-properly-define-boundaries-of-bounded-contexts" target="_blank">questions</a> that are closely related to current topic. What’s even more absurd is their dauntingly low votes and views number, in spite of this subject is so strategically important. The code residing in system services might be perfect, but it doesn’t really matter if <a href="https://medium.com/@wrong.about/wrong-ways-of-defining-service-boundaries-d9e313007bcc" target="_blank">service boundaries are identified incorrectly</a>, since there is no <a href="https://medium.com/@wrong.about/why-you-should-split-the-monolith-e946f57db38c" target="_blank">Business-IT alignment</a>, that both DDD and SOA are striving for. And it means inevitable project failure.