Service Monolith: Proposed OMC Anti-Pattern #2
Most software services developed and operated these days are increasingly more heterogeneous and distributed, and therefore, complex and hard to setup and manage. On top of all this, the rate of change seems to only go up. These trends can lead to an anti-pattern I’ve recently documented at the Open Management Consortium called “Service Monolith”:
Complex integrated software systems end up being maintained as a single opaque mass with no-one understanding entirely how it was put together, or of what elements it is comprised, and how they interact.
I describe some common rationale for using this anti-pattern and some of its consequences. There are positive design patterns to avoid or mitigate the anti-pattern, too. I find one interesting solution that seems to be becoming more ubiquitous and sort of side steps the deeper problem: virtualization. Virtualization is one strategy for dealing with producing these complicated systems. Using this strategy you get the whole conglomeration working on one host, cobbling the pieces together using the preferred recipe, then “freeze dry” it as an operating system image that you can instantiate on another host. With the image in hand an organization can “stamp it out” as needed. This technique seems to work for small scale deployments but I haven’t seen the approach work for maintaining large scale environments. Is this the sign of another emerging anti-pattern?
Edit (Damon 1/31/08):
This is a great quote by Kris Buytaert on his first booting of a vmware instance:
“And thus we joined the era of transferring an unmanagable image that everyone will copy around wile slightly modifying things and never placing them in version control . hence ending up one day with something nobody knows how we got there.”