Database Group Stable Counterparts

Overview

A central tenet of the Core Platform department is to enable other teams to be more self-sufficient in areas such as, in this case, the database. The Database Group is here to provide a helping hand in areas such as database design, query efficiency, database tooling and more. In order to be more efficient and to avoid diffusion of responsibility when providing database expertise to other groups, we are providing a list of database stable counterparts and which area of expertise is owned by each team member.

Stable Counterparts

If you have a need for database assistance please review the table below for the stable counterpart for your area. If one is not listed please feel free to reach out directly to the #g_database slack channel.

Responsibilities of the stable counterpart

1. Following the topic, knowing the latest updates (which makes us more efficient since we don’t all have to keep track of everything)
2. Actively work with the respective group, e.g. to implement a database design
3. Translate work from the topic into our group and involve other folks from our group to contribute as needed

Feature (alpha order)	Stable Counterpart	GitLab Handle
AI Tanuki Bot	Matt Kasa	@mattkasa
Background Migrations	Diogo Frazão	@dfrazao-gitlab
CI Partitioning	Simon Tomlinson	@stomlinson
Consumables Management (storage, compute, seats, usage, etc)	Kras Angelov	@krasio
Container Registry	Simon Tomlinson	@stomlinson
Database Testing Framework	Matt Kasa	@mattkasa
Database query intercepter	Jon Jenkins	@jon_jenkins
Embeddings Database	Matt Kasa	@mattkasa
Primary Key Migrations	Kras Angelov	@krasio
Table Size Reduction	Simon Tomlinson	@stomlinson
Vulnerability Management	Simon Tomlinson	@stomlinson
Work Items	Matt Kasa	@mattkasa