Salesforce
7 min read

Architecting Multi-System Production Platform: Event Processing Driving $400M+ Across 15,000+ Orgs

Read Full Article

Summary

The article discusses the architectural design and engineering challenges of Salesforce's Digital Wallet, a comprehensive consumption-based pricing visibility platform. It highlights the integration of legacy financial systems with modern data infrastructure, the implementation of failover strategies for low latency, and the development of robust monitoring systems to ensure billing accuracy. Key challenges included ensuring SOX compliance, managing metadata security, and achieving high availability across multiple organizations. The architecture leverages an event-driven approach to handle real-time usage tracking and integrates various systems to provide customers with insights into their consumption patterns.

Key Learnings

  • 1The importance of metadata security and compliance in systems that expose internal data to customers, necessitating the development of enforcement layers.
  • 2How an event-driven architecture can facilitate real-time data processing and integration across multiple systems while maintaining high availability.
  • 3The role of proactive monitoring and alerting in ensuring system reliability and accuracy in billing processes.
  • 4The necessity of architectural separation between usage tracking and billing to maintain data integrity and operational efficiency.

Who Should Read This

Senior Software Architects designing event-driven architectures for enterprise-scale applications

Test Your Knowledge

?

What trade-offs did the team consider when implementing the Strict System Mode for metadata security?

?

How did the architecture handle peak loads during billing periods, and what strategies were employed to ensure high availability?

?

What design decisions were made to integrate legacy systems with the new Digital Wallet platform, and what challenges did they face?

?

In what ways did customer feedback influence the development of features in the Digital Wallet, and how was this feedback incorporated into the architecture?

?

What are the implications of separating usage tracking from billing in terms of system design and operational processes?

Topics

Read Full Article at Salesforce

More articles about Event-driven Architecture

Explore Event-driven Architecture engineering →

More from Salesforce Engineering

View Salesforce engineering blogs →
Salesforce
6m

Engineering Platform Trust: Cutting Customer Case Volume 20x with Petabyte-Scale Health Signals

The article details the development of a Technical Health Score system at Salesforce, aimed at quantifying platform trust through analytics pipelines that handle petabytes of telemetry data. By...

Salesforce
5m

How Data 360 Optimized Kubernetes Scheduling Architecture, Delivering 13% Cost Savings

The article discusses how the Data 360 Compute Fabric team at Salesforce optimized Kubernetes scheduling to enhance resource efficiency and reduce costs. By evolving the default kube-scheduler...

Salesforce
6m

Delivering Accurate, Low-Latency Voice-to-Form AI in Real-World Field Conditions

The article explores the development of a hybrid architecture for a voice-to-form AI system used in field service applications. It highlights the integration of on-device speech-to-text capabilities...

Salesforce
7m

Hyperforce Migration at Scale: How Deterministic Automation Replaced Manual Spreadsheets Across 95,000 Organizations

The article outlines the development of the Migration Intake and Processing Service (MIPS) at Salesforce, which automates the migration of over 95,000 organizations to Hyperforce. It highlights the...

Salesforce
5m

Building an AI-Accelerated Compliance Automation Platform for 24x Faster Audits

The article outlines the development of FastTrack, a compliance automation platform by Salesforce, which significantly reduces audit execution time through AI-assisted development and API-based...