How we are closing the gap on replicating *everything* in GitLab Geo
Apr 29, 2021Michael Kozono

Summary
Introduced a new Geo replication and verification framework to reduce code duplication and make it easier for non-Geo engineers to add support for new data types. This framework includes a `Replicator` class and `Replicator strategy` concept for categorizing data like blobs and Git repositories. The event system was made more flexible and lightweight. The initial implementation focused on replicating newly created Package files, excluding replication of changes, deletes, backfills, and verification for the first iteration.
More from the High Availability trail
- Consolidate your GitLab stack with Gitaly on Kubernetes
- GitLab backs 99.9% availability SLA with service credits
- Downtime happens, but GitLab Incident Management can help
- How we tested a feature that affected (almost) all parts of GitLab
- Meet Praefect: The traffic manager making your Git data highly available