We migrated our PostgreSQL database with 11 seconds downtime (gds.blog.gov.uk)

Article summary

The UK government's GOV.UK Notify service migrated its PostgreSQL database from the GOV.UK Platform as a Service (PaaS) to Amazon Web Services (AWS) with only 11 seconds of downtime. The migration used AWS Database Migration Service (DMS) to transfer data from the source database to the target database. The team prepared for the migration by setting up a new database in their own AWS account, creating a DMS instance, and configuring VPC peering. The migration process involved a full load task, replication, and a final cutover to the new database.

Main themes

• database migration
• cloud computing
• data sovereignty
• geopolitical risks
• technical competence
• infrastructure management
• cost-effectiveness
• scalability and reliability

What commenters say

• The UK government's decision to migrate its database to AWS raises concerns about data sovereignty and reliance on a foreign company.
• Using a cloud provider like AWS can be more cost-effective and efficient than hiring and managing a team of sysadmins.
• The government's inability to hire and retain competent technical staff is a major obstacle to managing its own infrastructure.
• Outsourcing critical infrastructure and data to a foreign company poses significant geopolitical risks.
• The use of cloud services can lead to a loss of control and autonomy for governments and organizations.
• The benefits of using a cloud provider like AWS, including scalability and reliability, outweigh the potential risks and drawbacks.
• The UK government's migration to AWS is a necessary step to modernize its infrastructure and improve its services.
• The decision to use AWS rather than building its own cloud infrastructure is a pragmatic choice given the costs and complexity involved.