Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Salesforce Anti-Patterns

You're reading from   Salesforce Anti-Patterns Create powerful Salesforce architectures by learning from common mistakes made on the platform

Arrow left icon
Product type Paperback
Published in Nov 2022
Publisher Packt
ISBN-13 9781803241937
Length 206 pages
Edition 1st Edition
Concepts
Arrow right icon
Author (1):
Arrow left icon
Lars Malmqvist Lars Malmqvist
Author Profile Icon Lars Malmqvist
Lars Malmqvist
Arrow right icon
View More author details
Toc

Table of Contents (15) Chapters Close

Preface 1. Part 1: Technical Anti-Patterns
2. Chapter 1: Why You Need to Understand Salesforce Anti-Patterns FREE CHAPTER 3. Chapter 2: How Not to Mess Up Your System Architecture 4. Chapter 3: How Not to Get Confused about Security 5. Chapter 4: What Not to Do about Data 6. Part 2: Solution Anti-Patterns
7. Chapter 5: Unpicking Solution Architecture Troubles 8. Chapter 6: Keeping Integration Straight 9. Part 3: Process and Communication Anti-Patterns
10. Chapter 7: Keeping the Development Life Cycle from Going off Track 11. Chapter 8: Communication without Mistranslation 12. Chapter 9: Conclusion 13. Index 14. Other Books You May Enjoy

Muddling up the systems landscape

The easiest way to muddle up your systems landscape, as we shall see, is to go ahead with implementation in a local, unstructured, and badly governed way. While there are many attractions to small local projects, they very easily deteriorate into anti-patterns that have serious negative consequences for your overall enterprise architecture. We will start by looking at the classic Stovepipe anti-pattern, which is a common outgrowth of such projects, and then look at its organizational cousin, Stovepipe Enterprise.

Stovepipe

A stovepipe is a system that is built with no attention to standards or common abstractions, leading to a system that may work but is hard to maintain, extend, or interoperate with.

An example

John is the CRM manager at DreamCo, a provider of bespoke travel accessories. The company has decided to invest in a small implementation of Salesforce Sales Cloud, replacing an old Siebel system that’s been in operation...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €18.99/month. Cancel anytime