Answers are grounded in this paper and cite their sources.
Salesforce Database (SalesforceDB) is a multi-tenant relational database built by Salesforce to power the transactional workload of its Customer Relationship Management applications and platform. It is the system of record and an integral part of the Salesforce stack. Using its own database allows Salesforce to innovate from the database layer up and integrate the application's multi-tenancy into the database, enables the creation of new capabilities, optimizes operations, and improves security. Designed from the ground up to be cloud-native with a focus on high reliability and performance, it allows for simple, reliable cloud operations and scales to Salesforce's largest customers. The database manages customer data within the Salesforce infrastructure but is not directly accessible by customers. It is deployed in production across thousands of instances and dozens of regions around the world and holds many petabytes of data. This paper describes the motivation and innovative design of SalesforceDB. Like many modern databases, SalesforceDB is cloud-native and decouples compute and storage. Its design reflects Salesforce specific requirements: it natively supports multi-tenancy, employs a shared, immutable, distributed storage system, and uses a tenant-clustered log-structured merge tree (LSM) for data access. This enables it to support high levels of availability and durability, including tolerating availability zone (AZ) failures. SalesforceDB's architecture includes a novel LSM virtualization layer that facilitates tenant-level features that cannot be efficiently supported on existing database architectures. These include creating instant tenant copies, seamless tenant migration across database instances via metadata-only operations and efficient tenant-level encryption. Its shared-table multi-tenancy design minimizes per-tenant overhead. SalesforceDB's scale-out architecture leverages its shared LSM storage to achieve high scalability with minimal coordination.
No takes yet. Share an insight, caveat, or question.
Agrawal et al. (2026) studied this question.
Synapse has enriched 10 related papers. Consider them for comparative context: