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

Well done, you made it! This was the last chapter of the book and you are now an official anti-pattern aficionado.

In this chapter, we have summarized the main points of the book. In particular, we looked at six underlying factors that are common to many anti-patterns and are part of their root causes.

These provide signposts that architects can use to create an awareness of what anti-patterns are likely to occur in a given architectural context and what measures may be taken to mitigate them.

In order to use this knowledge in practice, we outlined two different approaches to incorporating anti-patterns into your architecture process. First, we looked at how to use it constructively for your own architectures and then how to use it diagnostically for examining existing architectures.

Finally, we looked at where you might go from here in order to expand your knowledge further. We outlined three pathways you might take and gave some suggestions for books and other...