Loosely-coupled communication

When inter-component communication is loosely coupled, we can more easily adapt to scaling influencers when they arise. First and foremost, a good inter-component communication design that's event-driven allows us to move components around. We can take a faulty or under-performing component out, and replace it with another. Not being able to substitute components this way means that we would have to fix the component in-place; a larger risk for delivering software and a scaling bottleneck from a development perspective.

Another beneficial side-effect of loosely coupled inter-component communication is that we can isolate problematic components when something goes wrong. We can prevent exceptions that occur in one component from leaving other components in a bad state, which just leads to further problems when the user tries to do something else. Isolating problems like this helps us scale our responses to fix faulty components.

Substituting components

Based on...