Bare metal to AWS in a one-hour window, and the code outlasted the handover.
Migrating a geospatial platform to AWS
- Sector
- Geospatial
- Duration
- 2 months
- Role
- Part of the implementation team
Where it started
A Java map application running on its own hardware, with a redundancy requirement on the location data. A migration like this is decided by the cutover window: how long the service is off while the data moves.
The decision
Define the whole destination as code before moving anything, so the environment could be stood up and rehearsed as many times as needed. The database was replicated across zones to meet the redundancy requirement, and administrative access narrowed to one controlled entry point.
What came of it
The cutover took an hour. And the repository outlived the handover: another DevOps engineer picked it up and kept working on it, which is the proof that the infrastructure stayed legible to someone who had not written it.
Something similar in front of you?
Get in Touch