GitLab High Availability Solutions
Dec 17, 2013Marc Radulescu

Summary
This post provides an overview of GitLab High Availability Solutions, discussing the trade-offs between increasing uptime and accepting complexity/cost. It structures the discussion starting with the simplest solution (server back-up) and gradually adds levels of complexity, including manual and automated snapshots, dedicated servers, slaves, and clustered/master-master filestore configurations. It emphasizes that there is no one-size-fits-all solution and that the page is a starting point for considering options.
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 are closing the gap on replicating *everything* in GitLab Geo
- How we tested a feature that affected (almost) all parts of GitLab