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

Org complications

In the Salesforce world, you don’t have to manage your underlying infrastructure, which frees you from a good number of potential temptations that can lead to anti-patterns. However, the way that you structure environments with different orgs in the Salesforce world is subject to a number of anti-patterns in its own right.

Ungoverned Org Proliferation

Ungoverned Org Proliferation is a Salesforce-specific anti-pattern due to a lack of defined org strategy, which leaves you with an ever-increasing number of unaligned orgs, eventually becoming architecturally unmanageable.

An example

Miranda has been hired as BigCo’s new CRM Migration Manager. The company has had a business unit approach to IT and does not have any centralized CRM capabilities at this point. Instead, three units use Salesforce mainly for opportunity management, and there are at least 15 other systems in use from a variety of vendors, as well as in-house developed systems in...