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 DevOps for Architects

You're reading from   Salesforce DevOps for Architects Discover tools and techniques to optimize the delivery of your Salesforce projects

Arrow left icon
Product type Paperback
Published in Jan 2024
Publisher Packt
ISBN-13 9781837636051
Length 260 pages
Edition 1st Edition
Concepts
Arrow right icon
Authors (2):
Arrow left icon
Rob Cowell Rob Cowell
Author Profile Icon Rob Cowell
Rob Cowell
Lars Malmqvist Lars Malmqvist
Author Profile Icon Lars Malmqvist
Lars Malmqvist
Arrow right icon
View More author details
Toc

Table of Contents (20) Chapters Close

Preface 1. Chapter 1: A Brief History of Deploying Salesforce Changes 2. Chapter 2: Developing a DevOps Culture FREE CHAPTER 3. Chapter 3: The Value of Source Control 4. Chapter 4: Testing Your Changes 5. Chapter 5: Day-to-Day Delivery with SFDX 6. Chapter 6: Exploring Packaging 7. Chapter 7: CI/CD Automation 8. Chapter 8: Ticketing Systems 9. Chapter 9: Backing Up Data and Metadata 10. Chapter 10: Monitoring for Changes 11. Chapter 11: Data Seeding Your Development Environments 12. Chapter 12: Salesforce DevOps Tools – Gearset 13. Chapter 13: Copado 14. Chapter 14: Salesforce DevOps Tools – Flosum 15. Chapter 15: AutoRABIT 16. Chapter 16: Other Salesforce DevOps Tools 17. Chapter 17: Conclusion 18. Index 19. Other Books You May Enjoy

Breaking up an existing monolithic application

Migrating a mature, monolithic application to Salesforce’s package development model can be a major undertaking filled with complexities and challenges.

On the complexity side, code refactoring is often needed to break tight couplings and fit components into modular packages. Dependency management becomes critical to untangle interconnected components. Introducing namespaces can add complexity in updating all references. Data models may need reworking to fit the new packaged schema. Permission sets and profiles will likely require redefinition. Automation and CI/CD pipelines need adaptation to handle packaging, versioning, and dependencies. Keeping various org environments in sync with the correct package versions is complex to orchestrate.

In terms of challenges, the transition will require extensive investment in resources and time. There will be a knowledge gap as teams learn the new model. Testing strategies need an overhaul...

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