Salesforce Messaging Architecture: Platform Events, Async Sends, and Multi-Tenancy at Scale
arXiv:2607.12943
The paper describes how to build a messaging system directly inside the Salesforce CRM, treating each message as a native record and using platform events and async sends to achieve scalable, multi‑tenant operation.
Abstract
Most enterprise messaging integrations function as external connectors. They reside outside the Customer Relationship Management (CRM) platform, receive webhooks, write peripheral logs, and consider the process integrated. Consequently, messages are isolated within the messaging platform while CRM records remain strictly inside the CRM, bridged only by fragile sync jobs, rigid field mappings, and eventual consistency windows. This paper outlines an alternative architectural paradigm: constructing the entire messaging core natively inside the CRM. Within this model, every message is treated as a native CRM record,every outbound path is a platform-native transaction, and all state parameters - including delivery status, opt-in metrics, conversation history, and record ownership - are stored as standard database objects. This structural native alignment allows the system to utilize standard reporting pipelines, operate inside native workflow builders, and trigger platform automation seamlessly. Drawing from a production managed package deployed across independent enterprise organizations spanning healthcare, sales operations, field services, and customer support, this study evaluates the core design patterns, platform scaling mechanics, multi-tenant decoupling constraints, and the boundaries of the platform-native architectural design.
8 pages, 1 table. An earlier version of this work was first posted on SSRN (DOI: 10.2139/ssrn.6903158)