Optimizing Salesforce for Scalable, Real-Time Performance
summary
Claims a runnable integration stack: MuleSoft with 300+ connectors as middleware, Salesforce APIs (REST, SOAP, Bulk) and platform events and CDC for near‑real‑time delivery with “millions of events per day” and replay guarantees. Performance relies on an EP measurement framework (page request → server → DOM → EP), governor limits, batch parallelism in Bulk API batch parallelism, OAuth2/JWT/SAML authentication, TLS and optional Shield encryption. Concrete recommendations include load testing, retry/dead‑letter queues and API layering; patterns are presented as proven to scale.
AI-written summary · about
chapters (10)
- 0:00Introduction and Overview
- 0:26Salesforce Integration Landscape
- 2:01API Architecture and Patterns
- 3:21Performance Measurement Framework
- 5:04MuleSoft Integration Capabilities
- 7:57Real-Time Integration Architecture
- 9:28Security and Governance Framework
- 11:01Scalability and Best Practices
- 13:34Key Takeaways and Next Steps
- 14:59Conclusion and Contact Information
related talks
20mHow AWS infrastructure addresses Salesforce’s resiliency goals
32mA Peek Inside the Enterprise Cloud at Salesforce
28mSalesforce Status Report – What Are We Up To With Spinnaker?
29mScaling Spinnaker for multi-region multi-cloud SaaS deployments
23mJust enough DevOps for data scientists.
42mThe Selenium Infrastructure
26mService Ownership: DevOps for Salesforce
18mBridging Legacy and Modern Systems