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

How Not to Mess Up Your System Architecture

This chapter will start with an explanation of how you mess up your system landscape by not retaining a disciplined approach to implementation and governance. We will then go through how coupling can become so tight that you create systems too fragile to use. Finally, we will look at some anti-patterns related to how you can structure orgs within an organization that uses Salesforce into multiple geographies and business units.

In this chapter, we’re going to cover the following main topics:

  • How the Stovepipe anti-pattern can leave us with systems that can only work in isolation and what you can do to avoid building stovepipes
  • What a Big Ball of Mud is, why a system can deteriorate into a state that fits this description, and how you can prevent it from happening to your system
  • How intense coupling makes systems fragile and potentially unusable, and how to draw clearer system boundaries that avoid this issue
  • ...