No matter how big a software system gets, it will still have a boundary. This boundary separates things inside the system from those outside it. In fact, you’d have noticed that dividing a large system into multiple components can have some great benefits. However, deciding how the system should be divided requires skill and understanding. Experience is the best teacher in such cases. But there are also some strategies that can help.
But what exactly does a boundary do?
A good software boundary keeps an application’s responsibilities, its rules, and the details needed to apply those rules together. Parts of the system outside this boundary can talk to things inside the boundary only through a clear pathway. This means that the skill of deciding boundaries requires you to have an idea of which responsibilities should be bunched together. Also, which dependencies should exist between them.
In this article, we’ll learn some key strategies that can help a developer make the right boundary-related decisions for the systems they are working on.
