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

Summarizing the key messages

In this book, we have covered dozens of anti-patterns across seven different architectural domains. However, it won’t have escaped the perceptive reader that many of the problems and suggested solutions are similar across several different patterns in seemingly different domains.

That indicates that, at a deeper level, anti-patterns have similar root causes that are often due to larger organizational or even psychological factors. Let’s look at some of these recurring causes:

  • Wishful thinking: Several anti-patterns are based on some form of wishful thinking – that is to say, not wanting to confront the technical reality in front of you. In Project Pieism, it is an inability to confront trade-offs and uncertainty; in Golden Hammer, it’s an overoptimistic belief in a single tool; and in Unplanned Growth, it’s the belief that a solution can be found later. Always be wary of optimism in technical architecture.
  • ...