This epic is intended to serve as a centralisation point for the overall organisation of the decomposition effort, not just the technical aspects. * Slack Channel: #wg_sec-database-decomposition * Technical Research And Decomposition Epic: https://gitlab.com/groups/gitlab-org/-/epics/13043 * Working Group Handbook Page: https://handbook.gitlab.com/handbook/company/working-groups/secure-govern-database-decomposition/ ## High Level Objectives/Reminders * [x] Configure initial `sec` database schema in GitLab and the GDK to initiate decomposition development. * [x] Determine the feasibility of Logical Replication and the proposed phased decomposition approach. * [x] Engage with the infrastructure team to instantiate the needed configurations for the `sec` database in GitLab.com * [ ] CNG and Omnibus configurations configured and created. * [x] [Decomposition Slice 1 - SBOM](https://gitlab.com/groups/gitlab-org/-/epics/14116) * 8 tables * [x] [Decomposition Slice 2 - Security & Dast](https://gitlab.com/groups/gitlab-org/-/epics/14196) * 16 tables * [x] [Decomposition Slice 3 - Vulnerabilities](https://gitlab.com/groups/gitlab-org/-/epics/14197) * 23 tables * [x] When decomposition is ready to begin infrastructure implementation, liaise with the Data Analytics team (Contact Point: @vedprakash2021 ) to enable them to begin testing SnowPlow data ingestion mechanics ahead of the tradeover as well. ## Rollout Timeline ```mermaid gantt dateFormat YYYY-MM-DD title Estimated Decomposition Timeline section Timeline Gitlab Application Work Ready :active, decompose, 2025-01-28, 2025-02-17 GitLab Decomposition Ready 17 February :milestone, rolloutready, after decompose, 0d Time left to finish rollout and communication plans :readycomms, 2025-01-28, 2025-03-019 Inform Customers of Planned Decomposition 19 March :milestone, communicate, 2025-03-019, 0d Infrastructure Rollout :inf, after communicate, 2025-04-19 Target Rollout Date 19 April :milestone, rollout, 2025-04-19, 0d axisFormat %Y-%m ``` ## Current Status - Application decomposition is just about ready, with us working on final sign offs - We're working on our rollout and communication plans to finalise the project ## Tips and Info ### FAQ See [Decomposition FAQ](https://gitlab.com/groups/gitlab-org/-/epics/13043#faq) for frequently asked questions ### Configure GDK for Sec DB development **NOTE:** While GDK can be configured to use a decomposed `gitlab_sec` DB, this is not recommended until Slices are complete as it can lead to unexpected behaviour due to foreign keys Run the following commands in your GDK. 1. `gdk config set gitlab.rails.databases.sec.enabled true` 2. `gdk reconfigure` 3. `rake db:create db:migrate` #### Configure a fully separate Sec database and connection. Should you need a fully separate Sec database for your changes, you will need to additionally set the following flag and reconfigure your GDK: `gdk config set gitlab.rails.databases.sec.use_main_database false` --- ## Follow-on work (2026) This working group completed the **Sec** decomposition. The playbook and lessons from it are now being reused for the next wave of database-pressure work, tracked under a new umbrella: * [&23180 — Reducing Main Database Pressure: Evaluating Solutions](https://gitlab.com/groups/gitlab-org/-/epics/23180) *(confidential)* — evaluates decomposition against other options (table-size reduction, retention, partitioning, app-level replication) for the AI and Merge Request domains. * [&23181 — Decompose AI Feature tables](https://gitlab.com/groups/gitlab-org/-/epics/23181) * [&23182 — Decompose Merge Request tables](https://gitlab.com/groups/gitlab-org/-/epics/23182) * [&23183 — A Generic Step-by-Step Guide to Decomposing GitLab](https://gitlab.com/groups/gitlab-org/-/epics/23183) — the reusable playbook distilled from this WG's work.