
4/29/2016 · Tomasz Maczukin
What this post added
This post provides a detailed breakdown of the infrastructure used for GitLab.com in April 2016, including the number of HAProxy load balancers, application stack servers (Nginx, Workhorse, Unicorn + Rails, Redis + Sidekiq), NFS servers, Redis, PostgreSQL, and Elasticsearch servers. It also details the use of Azure Availability Sets for HA and the infrastructure for managing Shared Runners, including autoscaled Docker machines. The post concludes with a total server count for GitLab.com.