Designing for Resilience: Building Architectures That Don’t Break at Scale

Explore how to anticipate and design around governor limits, API constraints, and release velocity. Participants sketch fault-tolerant architectures that recover gracefully when things fail.

Sample Scenario

• A rapidly growing enterprise runs its entire customer lifecycle on Salesforce — Sales, Service, and a custom-built fulfillment app. Over the last year, transaction volume has tripled, integrations have multiplied, and users are complaining about latency and data sync issues. Periodic release failures and API limit breaches are now common.

  The CTO’s directive: “We can’t afford downtime or data loss, but we also can’t freeze innovation.”

Participants are challenged to design a resilient Salesforce architecture that can handle scale, recover gracefully from failures, and maintain high availability without over-engineering.

Design Challenge:

• How do you design for resilience when the system is evolving fast, dependencies are growing, and you can’t slow down deployments?