Follow-up from "Add direction page for the Database Group"
The following discussions from !92135 (merged) should be addressed:
-
@joshlambert
started a discussion:The Database group is the steward of all relational database technologies at GitLab. It is responsible for growing GitLab's database expertise, promoting and supporting its proper use and making sure that there is continuity and no knowledge gaps as the GitLab team and product grow.
@iroussos - what do you think about more clearly stating the outcomes the database group wants to achieve, and then detailing how we plan to achieve those, much of which is already covered below?
For example outcomes could be a reliable, performant, and scalable relational database service, as well as a short cycle time for making changes that involve the database?
We could then get there by doing some of the items you mention above about knowledge, promoting proper use, and so on.
-
@joshlambert
started a discussionGitlab stores data in various ways and forms. There is Redis, which is used both as a cache and as a more lightweight semi-persistant storage. [..] But relational databases are the prominent persistent storage in GitLab, used for storing most of the user generated data in GitLab.
[..] would it perhaps be clearer to state that PG is the "common" relational data store linking all of GitLab together, while individual features may store their own content in data stores tailored for their use case? By volume it may not be true that PG stores the most.
-
@fzimmer
started a discussionThe database, as the prominent persistent storage used in GitLab, is at the core of all user interactions with a GitLab instance, as well as the layer that most automated GitLab features depend on. Any bottleneck at the database layer, regression or non performant application code that interacts with the database can break or render any lovable GitLab feature to a practically unusable one.
- I think it may help to expand the user experience angle and move it to the front.
- Can we make this more prominent?