Spring GDS 25th Anniversary
A logistics company that ships to 190 countries built something to ship to itself.
Disaster recovery is the plan and the machinery for getting systems back after something goes badly wrong. A region outage, a corrupted database, a deploy that takes production down, a ransomware hit. It's the answer to one question asked in advance: when this breaks, how do we get it running again, and how much do we lose along the way?
Two numbers define a recovery plan. RTO, the recovery time objective, is how long you can be down before it really hurts. RPO, the recovery point objective, is how much data you can afford to lose, measured as the gap back to your last good backup. An RTO of four hours and an RPO of five minutes describe very different systems and very different costs. Strategies range from cold backups you restore by hand to a hot standby in a second region that takes over automatically. A bank running a live replica that fails over in seconds is at the demanding end of that range.
Disaster recovery is distinct from a backup. A backup is a copy of data. Disaster recovery is the tested, rehearsed process for turning that copy back into a working system under pressure.
We set realistic RTO and RPO targets with clients before we design anything, because the right plan depends entirely on what an outage actually costs them. A marketing site and a payment system don't need the same answer, and pretending they do just wastes money or leaves a gap.
From there it's concrete work: automated backups, failover that's been tested rather than assumed, and recovery runbooks someone can follow at 3am without guessing. We fold this into platform standardization so recovery behaves consistently across the stack, watch cost optimization so resilience doesn't quietly double the bill, and use performance monitoring to catch the failure before it becomes the disaster. Companies come to us after a scare. We work through it with them so the next one is a non-event.
Sure your systems come back after a bad day? Let's make certain.
A logistics company that ships to 190 countries built something to ship to itself.
Turning a brand into a working business.
Half a million people. One app. Zero chaos.















