I’d be interested to hear more about the strategies you apply to structure your own apps that provide these benefits if you’re not using contexts (namespacing modules by business concern).
I suggest that without separation of concerns, apps often turn into monolithic great big balls of mud. Search for monolith and Rails or Django to see how much pain that causes.
By deciding to segregate your app by its business area from the outset, you invest a little more time thinking about the structure to ensure modules are highly cohesive within a context but contexts themselves are only loosely coupled. This allows you to extract a context into its own app, or its own standalone service (microservice) as usage and/or requirements dictate. It’s far easier to follow this path if the separation exists from day one as the boundaries and public API have already been defined and used.
