Salesforce Anti-Patterns (eBook)

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.

---

Avoid implementation failures and technical debt by mitigating anti-patterns in your Salesforce enterprise solutions using expert guidance and proven recommendationsPurchase of the print or Kindle book includes a free eBook PDFKey FeaturesBuild exemplary Salesforce architectures by studying anti-patterns that lead to failing systemsDemonstrate deep architectural principles that you can apply in your Salesforce projectsIdentify common problems in Salesforce architectures and apply better architectural solutionsBook DescriptionSalesforce 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.What you will learnCreate a balanced system architecture by identifying common mistakes around on- and off-platform functionality and interfacesAvoid security problems that arise from anti-patterns on the Salesforce platformSpot common data architecture issues and discover intuitive ways to address themAvoid the dual traps of over- and under-customization in your solution architectureExplore common errors made in deployment setups, test strategy, and architecture governanceUnderstand why bad communication patterns are so overlooked in architectureWho this book is forThis book is for Salesforce architects, aspiring architects, developers, consultants, and decision makers who want to start making the right architectural choices or prepare for their journey to CTA. This book helps you gain a professional understanding of Salesforce and its building blocks. It is not code-centric, so you will benefit from both functional and technical experience, but a basic level of platform understanding is required.]]>