Database Excellence: rosters, stage mission, and the Self-Managed Database Experience team

    click DBF "/handbook/engineering/data-engineering/database-excellence/database-frameworks"

    DE --> DBO[Database Operations]

    click DBO "/handbook/engineering/data-engineering/database-excellence/database-operations"

    DE --> DBH[Database Health]

    DE --> SMDX[Self-Managed Database Experience]

    click SMDX "/handbook/engineering/data-engineering/database-excellence/self-managed-database-experience"

```

## Mission

Keep GitLab's databases running reliably through proactive health management, operational excellence, and strategic enablement. We maintain operational runway by identifying and mitigating saturation points, operate infrastructure with automated and scalable processes, and provide tools and frameworks that help teams build features sustainably. While our primary focus is GitLab.com, we are expanding our scope to provide database health frameworks and tooling that benefit self-managed customers as well.

Keep GitLab's databases reliable and inside their runway, on GitLab.com and for the customers who run GitLab themselves. On GitLab.com that means running the Postgres fleet, staying ahead of saturation by controlling data growth rather than only adding hardware, and building one managed path for every product database, including Cells. For self-managed customers it means an upgrade they can trust: integrity checks that gate it, a test framework that guarantees every migration runs, and a shorter path through it. Across all of it, we make database review scale with the codebase so teams can build sustainably with data without a small group of reviewers becoming the bottleneck.

## Stage Leadership

* Preventing database performance issues before they reach production

* Establishing and maintaining data lifecycle best practices

{{< group-by-slugs alexander-sosna imanpalsingh l.rosa maximeorefice panoskanell praba.m7n vporalla >}}

{{< group-by-slugs alexander-sosna amritasinha l.rosa mattkasa maximeorefice panoskanell praba.m7n vporalla >}}

### Database Health

### Self-Managed Database Experience

The [Database Health](/handbook/engineering/data-engineering/database-excellence/database-health/) group provides the monitoring, observability, and health frameworks that keep databases healthy across both GitLab.com and self-managed deployments, including shift-left identification of saturation points.

The [Self-Managed Database Experience](/handbook/engineering/data-engineering/database-excellence/self-managed-database-experience/) group provides the monitoring, observability, and health frameworks that keep databases healthy across both GitLab.com and self-managed deployments, including shift-left identification of saturation points.

Priorities:

* Providing visibility into database health across all deployment types

* Optimizing database resource utilization and cost efficiency

{{< group-by-slugs alexives krasimirangelov meiyang nbelokolodov rhenchen.gitlab stomlinson >}}

{{< group-by-slugs nbelokolodov amsingh6 imanpalsingh krasimirangelov >}}

### Database Automation

* Building reusable tooling for database provisioning, configuration, and upgrades

* Enabling reliable, repeatable database operations across deployment types

{{< group-by-slugs dazhu1 bshah11 saadullah707 mattkasa jon_jenkins pmistry2 amritasinha amsingh6 >}}

{{< group-by-slugs dazhu1 bshah11 jon_jenkins meiyang pmistry2 rhenchen.gitlab saadullah707 >}}

### Previous Teams

The [Database Operations](/handbook/engineering/data-engineering/database-excellence/database-operations) group managed the infrastructure and automation that power GitLab.com's PostgreSQL databases.

#### Database Health

The [Database Health](/handbook/engineering/data-engineering/database-excellence/database-health/) group ran from the FY27-Q1 reorganization until September 2026, when its self-managed health work moved to Self-Managed Database Experience and its GitLab.com saturation work moved to Database Automation.

## How We Work

Each team within Database Excellence is composed of a mix of backend engineers and reliability engineers (SRE/DBRE). The balance varies by team — Database Architecture and Database Health are primarily backend engineers, while Database Automation is primarily reliability engineers — but every team has both disciplines represented.

Each team within Database Excellence is composed of a mix of backend engineers and reliability engineers (SRE/DBRE). The balance varies by team: Database Architecture and Self-Managed Database Experience are primarily backend engineers, while Database Automation is primarily reliability engineers. Every team has both disciplines represented.

While each team has a distinct focus area, several responsibilities are shared across the entire stage. Database reviews are coordinated by Database Architecture but staffed by members of all three teams. Oncall rotations draw from reliability engineers across the stage. Operational needs such as saturation mitigation and incident response are distributed across all teams rather than owned by any single group. Infrastructure management and database upgrades are also shared across teams, as the regional distribution of the three groups — spanning AMER, EMEA, and APAC — enables the potential for follow-the-sun coverage. This shared model ensures that operational knowledge stays broad and no single team becomes a bottleneck.

The team is composed primarily of backend engineers, with reliability engineers to help achieve its infrastructure and operational goals. Regardless of role, all team members share stage-level responsibilities including database reviews, oncall rotations, and operational needs alongside the other Database Excellence teams.

{{< group-by-slugs alexander-sosna imanpalsingh l.rosa maximeorefice panoskanell praba.m7n vporalla >}}

{{< group-by-slugs alexander-sosna amritasinha l.rosa mattkasa maximeorefice panoskanell praba.m7n vporalla >}}

The team is composed primarily of reliability engineers, with backend engineers to help achieve its tooling and framework development goals. Regardless of team, all team members share stage-level role responsibilities including database reviews, oncall rotations, and operational needs alongside the other Database Excellence teams.

{{< group-by-slugs dazhu1 bshah11 saadullah707 mattkasa jon_jenkins pmistry2 amritasinha >}}

{{< group-by-slugs dazhu1 bshah11 jon_jenkins meiyang pmistry2 rhenchen.gitlab saadullah707 >}}

---

title: "Database Health Team"

description: "The Database Health team maintains operational runway for GitLab's databases through health monitoring, observability, shift-left saturation identification, and health frameworks for both GitLab.com and self-managed deployments."

description: "The Database Health team ran from early FY27 until September 2026, when its scope was split between Self-Managed Database Experience and Database Automation."

---

The Database Health team is the result of a split of the [Database Frameworks Team](/handbook/engineering/data-engineering/database-excellence/database-frameworks/).

The Database Health team was one of the three teams created in the FY27-Q1 reorganization, from a split of the [Database Frameworks Team](/handbook/engineering/data-engineering/database-excellence/database-frameworks/). In September 2026 it wound down and its scope was split along the line that had always run through it: GitLab.com and self-managed.

## Mission

## Where the work went

Maintain operational runway for GitLab's databases by proactively identifying and mitigating saturation points before they impact customers. We provide the visibility, tooling, and frameworks that keep databases healthy across both GitLab.com and self-managed deployments.

* **Self-managed health frameworks**, along with the upgrade and migration work that had been planned for a separate Database Migrations team, went to the new [Self-Managed Database Experience](/handbook/engineering/data-engineering/database-excellence/self-managed-database-experience/) team.

* **GitLab.com health monitoring, shift-left saturation identification, and managed Postgres monitoring** went to [Database Automation](/handbook/engineering/data-engineering/database-excellence/database-automation/), together with the engineers doing that work.

## Scope

Identifying and mitigating active saturation points remains a shared responsibility across all Database Excellence teams, as it was when this team existed.

The Database Health team is responsible for:

## What the team did

* **Database health monitoring & observability** — Building and maintaining the dashboards, metrics, and monitoring systems that provide visibility into database health across GitLab.com and self-managed instances.

* **Shift-left saturation identification** — Developing tooling and processes that detect potential saturation points earlier in the development cycle, before they reach production. Identifying and mitigating active saturation points is a shared responsibility across all three Database Excellence teams.

* **Self-managed health frameworks** — Building frameworks that give self-managed customers insight into the health and operability of their GitLab database, bringing the same visibility available on GitLab.com to customer-managed environments.

Database Health's mission was to maintain operational runway for GitLab's databases by proactively identifying and mitigating saturation points before they impacted customers, and to provide the visibility, tooling, and frameworks that keep databases healthy across both GitLab.com and self-managed deployments. Its scope was:

## Team

The team is composed primarily of backend engineers, with reliability engineers to help achieve its infrastructure and operational goals. Regardless of role, all team members share stage-level responsibilities including database reviews, oncall rotations, and operational needs alongside the other Database Excellence teams.

{{< group-by-slugs alexives krasimirangelov meiyang nbelokolodov rhenchen.gitlab stomlinson >}}

* **Database health monitoring and observability**: dashboards, metrics, and monitoring systems for database health across GitLab.com and self-managed instances.

* **Shift-left saturation identification**: tooling and processes that detect potential saturation points earlier in the development cycle, before they reach production.

* **Self-managed health frameworks**: frameworks that give self-managed customers insight into the health and operability of their GitLab database.