Docusign Modernizes E-Signature Data Platform with Azure SQL
Docusign, the global leader in electronic signatures and Intelligent Agreement Management (IAM), has modernized its core e-signature stack by moving complex on-premises workloads to Microsoft Azure. The company’s eSignature services are used by over 1.9 million customers and a billion people in 180 countries for daily transactions. Slow or unavailable agreements can delay sales, hires, renewals, or payments, slow hospital admissions, prevent bank account openings, and interrupt hotel check-ins.
Docusign’s primary database, DocusignDB (DSDB), had grown to 308 TB across five production sites with more than 500 tables and 8,000 stored procedures. At peak, the hottest DSDB instance generated two to three times the I/O demand of a top-tier Azure M176 configuration. The sheer size of the monolithic database made it increasingly difficult to meet performance benchmarks required by the eSignature application.
The company’s Senior Principal Engineer, Josh Meier, notes that as demand grew, DSDB’s production environment began approaching its practical capacity with engine-level contention constraining throughput at the busiest site. A 1:1 migration would have carried the same scalability constraints forward, while moving accounts individually introduced unacceptable cross-datacenter latency.
Docusign needed an architecture that could sustain growing transaction volumes and maintain predictable application performance without changing the customer experience or API contract. To meet this demand, Docusign decomposed its core database environment through vertical and horizontal sharding across custom Azure SQL configurations and services.
The company worked with Microsoft SQL Engineering to validate the Azure SQL design. For new and feature-specific databases, Docusign uses Azure SQL managed database services. EnvelopeSearchDB (ESDB) runs on Azure SQL Database Hyperscale, providing a consolidated search view across DSDB and EVDB with read replicas and independent compute and storage scaling.
Azure SQL Database Hyperscale re-architects the traditional database engine around distributed storage, separated compute and storage, and scalable cloud-native infrastructure. This technology future-proofs even small SQL workloads and scales to meet changing requirements. For the largest DSDB workloads, Azure SQL virtual machines provided the configuration control and sizing required.
Docusign executed a sub-five-minute site-level database failover followed by a controlled EVDB ramp, validated with 35,000 test cases and over 50 runbook rehearsals. The team moved nearly 200 million accounts across five production sites while eSignature stayed live without rewriting the application or experiencing a big-bang customer migration.
The resulting architecture lets Docusign shard the transactional envelope workload while preserving a unified search experience. As EVDB adds shards and envelope history moves from DSDB, ESDB can expand storage, compute, and read capacity independently without rebuilding the application or search architecture.
Docusign is now moving more eSign services onto its Kubernetes-based platform and decommissioning on-premises datacenters. The company’s Senior Principal Engineer notes that this modernized Azure foundation provides the scale to power IAM and AI capabilities, including Docusign Iris, the engine powering Docusign’s AI contract management platform.
The new architecture also enables AI-assisted agreement summaries, real-time signer Q&A, and AI agents automating redlines. The company’s Fellow, Abhishek Chaturvedi, notes that this modernized foundation provides a path to scale throughput as demand increases without compromising availability, latency, security, or compliance.