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

What Not to Do about Data

This chapter is about the ways in which you can compromise your data layer on the Salesforce platform. Throughout this chapter, we cover four data domain anti-patterns that occur with some frequency in Salesforce environments and give you pointers on how to recognize and avoid them.

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

  • Why treating Salesforce as a relational database won’t lead to acceptable results
  • How failing to coordinate activities can lead to a disconnected data model with serious negative repercussions
  • The negative consequences of failing to plan for growth in your database, especially when you should know better
  • Why data synchronization can be a great solution on a small scale, but a nightmare on a larger scale

After completing this chapter, you will have a good understanding of how Salesforce is different from a traditional relational database and why that matters greatly. You...