How Not to Mess Up Your System Architecture
This chapter will start with an explanation of how you mess up your system landscape by not retaining a disciplined approach to implementation and governance. We will then go through how coupling can become so tight that you create systems too fragile to use. Finally, we will look at some anti-patterns related to how you can structure orgs within an organization that uses Salesforce into multiple geographies and business units.
In this chapter, we’re going to cover the following main topics:
- How the Stovepipe anti-pattern can leave us with systems that can only work in isolation and what you can do to avoid building stovepipes
- What a Big Ball of Mud is, why a system can deteriorate into a state that fits this description, and how you can prevent it from happening to your system
- How intense coupling makes systems fragile and potentially unusable, and how to draw clearer system boundaries that avoid this issue ...
