Exploring loosely coupled architecture

Alright, in a vacuum, loosely coupled architecture seems like a bad idea. You disperse your components so much that there is no rhyme or reason as to how any information gets from one place to another. You can’t count any sort of consistent time for all your data to collate into one place for the thing you want to happen to actually happen.

However, there are a few factors that make loosely coupled architecture so effective in a practical setting. These factors are both philosophical and architectural. Firstly, no matter how well you design a system, it will fail somewhere at some time. The loosely coupled architecture allows the system to fail gracefully and to recover from failures in a way that doesn’t affect other components and users of the system. Because each component is isolated, these components can be identified after a single failure (a lot of the time, a clone component will succeed). This failure can be logged and...