Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
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

Communicating too much

This section will explore what happens when you communicate too much in a technical context. To do this, we will start by exploring an anti-pattern taken straight out of cognitive psychology: cognitive overload.

Cognitive overload

Cognitive overload happens when the amount of information presented becomes overwhelming to the recipient to the extent that it impairs action.

Example

LilacCo, the world’s leading producer of scented candles, is having major issues with its integration landscape. It has a relatively recently purchased MuleSoft platform, but it has seen little use, and most integrations still run through legacy middleware or point-to-point.

Martin is a technical architect who has been given the task to come up with a solution to the various issues LilacCo is experiencing. The issues include high latency and slow performance on many integrations, poor logging and monitoring, long and error-prone development cycles, and the inability...

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 $19.99/month. Cancel anytime
Banner background image