Book Image

Salesforce Anti-Patterns

By : Lars Malmqvist
Book Image

Salesforce Anti-Patterns

By: Lars Malmqvist

Overview of this book

Salesforce Anti-Patterns teaches you to spot errors in Salesforce patterns that may seem like a good idea at first but end up costing you dearly. This book will enable Salesforce developers and architects to understand how ingenious Salesforce architectures can be created by studying anti-patterns and solutions to problems that can later lead to serious implementation issues. While there are several books on the market that start with the question, “How do I create great Salesforce architecture?” and proceed to a solution from there, this book instead starts by asking, “What tends to go wrong with Salesforce architectures?” and proceeds to a solution from there. In this book, you’ll find out how to identify and mitigate anti-patterns in the technical domains of system architecture, data architecture, and security architecture, along with anti-patterns in the functional domain of solution architecture as well as for integration architecture. You’ll also learn about common anti-patterns affecting your Salesforce development process and governance and, finally, how to spot common problems in how architects communicate their solutions. By the end of this Salesforce book, you’ll have gained the confidence to architect and communicate solutions on the Salesforce platform while dodging common mistakes.
Table of Contents (15 chapters)
1
Part 1: Technical Anti-Patterns
6
Part 2: Solution Anti-Patterns
9
Part 3: Process and Communication Anti-Patterns

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...