We are splitting our database into Main and CI

GitLab is undertaking a significant architectural change to improve the performance and scalability of GitLab.com by splitting its single PostgreSQL database into two clusters: a main database for general features and a ci database for Continuous Integration-related features. This process, known as functional decomposition, is expected to double the database capacity and enhance performance by increasing available database connections and reducing congestion during peak hours. It promises increased stability by shifting ci writes to a separate cluster, thereby reducing database saturation and related incidents, and allowing more focus on new feature development. The implementation will require a planned downtime of up to 120 minutes on July 2, 2022, during which GitLab.com users will experience complete service disruption. Despite added complexity, GitLab ensures tool and dashboard reusability and has prepared extensively with over 600 merge requests, phased rollouts, and thorough rehearsals to minimize risks and ensure a smooth transition.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.