Monika: A lesson in component based design
I was giving a lecture on architecture recently, and the notion of components came in. The most important bit about that lecture was probably at the very end, when I discussed what it is that I consider to be a component. During that discussion, I introduced Monika, the payment processing component.
Monika has the following Service Level Agreement:
- Payment initiation is done messages.
- Notification about payment completion is handled via a callback REST call.
- The SLA calls for 90% of all successful payments to be processed in 2 business days.
So far, it doesn’t sound really complicated, right? And there isn’t even a hint of how Monika works in the SLA or the contracts.
This is Monica:
Well, not really, but it makes the point, doesn’t it.
Monica is a component in the system that respond to (SMTP) messages, does some work, and respond by clicking on a link in the email (REST call).
Monica has a really sucky SLA, since she has only 22% uptime over the course of the year, and then there are those two weeks when she has her yearly maintenance period (vacation), etc.
The most important thing about this is that we are able to abstract all of that away and treat this scenario as just another component in the system.
All too often, people hear components and they start thinking about things like this:
A component in a system is usually something much larger than a single class or a set of classes. It is an independent agent in the system that has its own behavior, resources, dedicated team and deployment schedule separate from all other components.