Stories in Architecture

Salesforce Engineering addressed the challenge of monitoring enterprise org health at scale by moving beyond static reports to an in-app experience called Salesforce Health Insights. The team needed to correlate point-in-time configuration metadata with continuously changing runtime telemetry across systems that lack shared identity models.

To solve this, they built a harmonization layer that reconciles fragmented datasets and maps runtime activity to individual metadata components while accounting for traffic volume and seasonality. This architecture maintains clear boundaries between deterministic findings and external operational context, preserving data origin and freshness information.

The initiative expanded from roughly one hundred initial security signals to over four hundred covering process automation, customization, and agentic readiness. Each signal follows standardized metadata rules and remediation guidance derived from the Salesforce Well-Architected Framework and known system hotspots.

Findings are prioritized using operational context such as application CPU usage and peak business hour traffic to determine criticality and required effort. The system uses a headless schema that emits raw JSON for any user interface or agent, supports an MCP interface, and can deliver summaries directly to Slack channels.

The team built a unified architecture to deliver real-time mobile personalization across iOS, Android, React Native, and Flutter. They solved platform fragmentation by establishing consistent schemas and event semantics while allowing each technology stack to use its native rendering capabilities. A bridge layer enables React Native and Flutter to access native APIs through iOS and Android, preserving a single SDK interface for developers.

Developers define stable content zones and register approved native components once. Marketers then configure templates, targeting, and component selection through the Salesforce user interface. The platform serves this metadata via a global CDN, and the mobile SDK applies the rules to dynamically render the correct native element without requiring new app builds.

Real-time identity resolution relies on Data 360 to merge anonymous web, email, and mobile interactions into a single profile during authentication. Decisioning runs entirely on the server, so the SDK only receives final experience instructions rather than raw customer data. Teams can validate targeting and layout using a QR code preview flow that injects live profile attributes into the simulator before launch.

Introduces the challenge of scaling Experience Cloud portals for multiple independent organizations, each managing its own identity infrastructure and security standards. Relying on separate login paths and manual configurations quickly creates bottlenecks during onboarding.

Proposes using the account record as the central anchor for external user management. The user to contact to account relationship provides a stable context for storing identity provider preferences, authentication configurations, and onboarding status. This design keeps organization scoped policies centralized and easily retrievable.

Details the implementation steps, including configuring Login Discovery to route users based on account level settings instead of presenting multiple login buttons. Data access follows this same model by aligning lookup relationships with appropriate sharing mechanisms like Sharing Sets or standard Sharing Rules. These choices directly impact community license selection and must align with least privilege principles.

Concludes that treating onboarding as a configuration exercise rather than a deployment project allows administrators to bring new organizations online predictably. The approach reduces architectural complexity while maintaining secure, scalable access controls across the portal.

Salesforce has released an updated version of its Well-Architected Framework to address growing architectural complexity and the rise of autonomous agents. The previous three-pillar model focused on trusted, easy, and adaptable solutions, while the new structure expands to five distinct categories.

The revised framework organizes guidance around trust, reliability, operational excellence, resource and cost optimization, and fairness. Each pillar includes a dedicated lens that examines how these principles apply when designing systems where agents can reason and take action across multiple platforms.

The update emphasizes architectural trade-offs, noting that optimizing for one quality often impacts another. Salesforce developed the framework through collaboration with the Office of the Chief Architect and feedback from hundreds of practitioners. The complete guidance is now available on the Architecture Center for immediate use.

Cloud Atlas is the globally distributed identity data store behind a large share of Salesforce logins and token validations, run to five nines of availability. In this interview, the team’s engineering lead explains why overload at that layer is dangerous: slow responses cause upstream services to retry, the retries add traffic to a system already under pressure, and a local bottleneck spreads. Agent-driven and automated workloads have made traffic burstier and harder to predict than human logins.

The old protection was per-instance rate limiting. That held up while infrastructure was static, but with autoscaling each server’s limits went stale whenever instances were added or removed, and each server knew only its own load rather than a customer’s total usage across the fleet. Busy servers rejected requests while capacity sat idle elsewhere, and one tenant’s spike could still starve others.

The redesign protects the service as a whole instead of individual servers. It combines global quota management that needs no central coordinator with load shedding that acts before retries begin to amplify the overload, so a single customer’s surge is isolated rather than shared.