## Background Migrations GitLab container registry background migrations are essential for performing large or complex database changes without affecting system performance or user experience. When dealing with large datasets or structural changes to the database, these migrations can be time-consuming and resource-intensive. Running them in the background allows these operations to be spread over time, minimizing the risk of system slowdowns, database locking, or downtime. This ensures that GitLab container registry remains operational while the migration is in progress, with minimal impact on users. Ultimately, background migrations enable GitLab container registry to scale and adapt while keeping the user experience smooth and uninterrupted. As we build out new features of the container registry, more use cases like https://gitlab.com/gitlab-org/container-registry/-/issues/973+ will benefit greatly from being able to run background migrations. This epic encapsulates all the effort required to implement and release a registry background migration process