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

Communicating too much

This section will explore what happens when you communicate too much in a technical context. To do this, we will start by exploring an anti-pattern taken straight out of cognitive psychology: cognitive overload.

Cognitive overload

Cognitive overload happens when the amount of information presented becomes overwhelming to the recipient to the extent that it impairs action.

Example

LilacCo, the world’s leading producer of scented candles, is having major issues with its integration landscape. It has a relatively recently purchased MuleSoft platform, but it has seen little use, and most integrations still run through legacy middleware or point-to-point.

Martin is a technical architect who has been given the task to come up with a solution to the various issues LilacCo is experiencing. The issues include high latency and slow performance on many integrations, poor logging and monitoring, long and error-prone development cycles, and the inability...