You're reading from Becoming a Salesforce Certified Technical Architect Prepare for the review board by practicing example-led architectural strategies and best practices

Product type Paperback

Published in Feb 2021

Publisher Packt

ISBN-13 9781800568754

Length 628 pages

Edition 1st Edition

Tools

Salesforce

Concepts

Software Architecture

Author (1):

Tameem Bahri

View More author details

Table of Contents (21) Chapters

Preface

1. Section 1: Your Journey to Becoming a CTA

2. Chapter 1: Starting Your Journey as a CTA FREE CHAPTER

3. Chapter 2: Core Architectural Concepts – Data

4. Chapter 3: Core Architectural Concepts – Integration and Cryptography

5. Chapter 4: Core Architectural Concepts – Identity and Access Management

6. Section 2: Knowledge Domains Deep Dive

7. Chapter 5: Developing a Scalable System Architecture

8. Chapter 6: Formulating a Secure Architecture in Salesforce

9. Chapter 7: Designing a Scalable Salesforce Data Architecture

10. Chapter 8: Creating a Lean Solution Architecture

11. Chapter 9: Forging an Integrated Solution

12. Chapter 10: Development Life Cycle and Deployment Planning

13. Chapter 11: Communicating and Socializing Your Solution

14. Section 3: Putting It All Together

15. Chapter 12: Practice the Review Board – First Mock

16. Chapter 13: Present and Defend – First Mock

17. Chapter 14: Practice the Review Board – Second Mock

18. Chapter 15: Present and Defend – Second Mock

19. Other Books You May Enjoy

Appendix: Tips and Tricks, and the Way Forward

Integration in the enterprise – understanding the landscape

The digital enterprise landscape is continuously becoming more sophisticated. Gone are the days when the enterprise used to have less than 10 systems covering most of its business processes. Today's enterprises have hundreds, if not thousands, of different applications that are either bought, built in house, or a combination of both. This is in addition to a set of legacy systems that are still surviving the axe. Nowadays, it is very common to find that an enterprise has dozens of websites, multiple instances of ERP systems, and many other departmental applications, in addition to several data warehouses or lakes.

One of the reasons why enterprises end in such situations is because of the complexity associated with building business applications. Building a single application that runs all business processes is nearly impossible. Maintaining it and adapting to day-to-day business challenges and requested changes...