Skip to main content
All cases

Francisco's engineering background

A migration between cloud accounts with no application downtime.

Client: NASDAQ-listed biotech company

The result

0
minutes of application downtime
30 min
window for the database
235
tables verified after the cutover
3 weeks
with the old database kept as a fallback

Project from June to August 2026.

Francisco's work as the lead DevOps engineer for the cutover, outside ResonateOps. The data copy was run by the client's database administrator.

The problem

A production application had to move to a new cloud account, with a different deployment platform and a different database, without stopping its users.

The target database ran an older version than the source, so neither a direct copy nor standard replication would work.

What we built

  • Phase 1, the application (June 16, 2026): the new version ran against the old database and the switch was a DNS change with instant rollback. No downtime.
  • Phase 2, the database (August 5, 2026): history was copied in advance and only the tail moved during the window. A 30-minute cutover.
  • A full rehearsal two weeks earlier, pointing the staging environment at the new database.
  • The old database stayed untouched as a fallback for three more weeks, until August 26.

Tools

AWSKubernetes (EKS)PostgreSQLAuroraRoute 53Spinnaker

Want a system like this in your company?

Let's talk for 15 minutes about your company.

You tell me what you want solved and I tell you what AI can do today, how long it takes and whether it makes sense for you. If it is not a fit, I say so on the same call.