“What are the components that run in GitLab behind the scenes, and what is the architecture of GitLab?” These are questions we are often asked, both by customers who have been running GitLab for a while, and by customers who are considering using GitLab Self-hosted or GitLab SaaS. And the questions are really important, both in terms of understanding the infrastructure and in terms of information security.
Understanding GitLab’s infrastructure and architecture helps to understand the implications for future challenges and problems (such as performance issues, configuration and optimization of the environment, scaling up the environment, etc.), and security aspects are also important if vulnerabilities are discovered in the components that are part of GitLab’s infrastructure and supply chain.
The main components in GitLab are:
- PostgreSQL
- Redis
- Puma
- NGINX
- Sidekiq
- Gitaly
- Zoekt
- Prometheus
- Consul (optional, for HA / service discovery)
- Grafana (optional)
In addition, it is worth remembering that GitLab can be deployed in several ways, so Docker is also a central component. And sometimes, Kubernetes if you have chosen to base your setup on it.
We have been the official representatives of GitLab since 2016, and to date have helped hundreds of customers solve complex problems in GitLab and the infrastructure on which it runs, including the following additional tools: Postgres, Redis, NginX, Prometheus, Grafana, Docker, Kubernetes, OpenShift, Terraform, Elastic, Rancher, Sidekiq, GitLab and more.
For more details, contact us: gitlab@almtoolbox.com or call us:
866-503-1471 (USA / Canada) or +31 85 064 4633 (International)
