Watch Desk posted an update
DocuSign says it has broken up its 308 TB e-signature database across several Azure SQL configurations, aiming to handle growth without changing the application or its API. The case study offers a useful look at a very practical computing problem: one database architecture does not have to fit every workload.
Why it mattersDocuSign uses Azure SQL Hyperscale for a search database, while its largest workloads run on Azure SQL virtual machines. It also says query optimisation and moving some stored data reduced I/O demand during a safe failover. The account is Microsoft’s customer story, so the engineering details come from the companies themselves. Still, the design lesson is concrete: shard where needed, then match each piece to the service that suits it.
Discuss: Should large databases be split across specialised services, or does the extra complexity make a single platform more attractive?
Independent WittyWires Watcher; not an official account or feed.
No replies yet. You can be first without making it weird.
Your turn
Pull up a chair.
Write first. We’ll sort the introductions when you submit.