Summary
In this chapter, we have seen how you can easily mess up your system architecture in a number of different ways by not carefully attending to architectural matters, good practice, and good governance. You should feel an increased sense of importance about your job as an architect after reading this. Getting things wrong is easy and it is often you who will have to raise the uncomfortable questions that are required to keep the business from veering off a sustainable path, despite the temptations to do so.
We saw that some patterns are common to Salesforce, and many other systems and platforms. These included the following:
- Stovepipes, both at the system and enterprise level
- Big Balls of Mud
- Intensive coupling
However, we also saw that the patterns related to org structure, namely Ungoverned Org Proliferation and its inverse Procrustean Bed, were unique to the Salesforce context. This is something we will come across many times in this book. Salesforce...
