News for hackers. Stuff that matters.

A comment on My Notes on Gitlab's Postgres Schema Design (2022). Parent comment

Re:My Notes on Gitlab's Postgres Schema Design (2022) by mvdtnz on Saturday February 17, 2024 @09:05PM (#39415447)
Do we know for sure if gitlab cloud uses a multi-tenanted database, or a db per user/customer/org? In my experience products that offer both a self hosted and cloud product tend to prefer a database per customer, as this greatly simplifies the shared parts of the codebase, which can use the same queries regardless of the hosting type.

If they use a db per customer then no one will ever approach those usage limits and if they do they would be better suited to a self hosted solution.

[ Parent | on HN ]
Re:My Notes on Gitlab's Postgres Schema Design (2022) by Maxion on Sunday February 18, 2024 @02:45AM (#39417049)
I've toyed with various SaaS designs and multi tenanted databses always come to th forefront of my mind. It seems to simplify the architecture a lot.
[ Parent | on HN ]
Re:My Notes on Gitlab's Postgres Schema Design (2022) by tcnj on Sunday February 18, 2024 @03:07AM (#39417149)
Unless something has substantially changed since I last checked, gitlab.com is essentially self-hosted gitlab ultimate with a few feature flags to enable some marginally different behaviour. That is, it uses one multitennant DB for the whole platform.
[ Parent | on HN ]
Re:My Notes on Gitlab's Postgres Schema Design (2022) by karolist on Sunday February 18, 2024 @09:35AM (#39419393)
Not according to [1] where the author said

> This effectively results in two code paths in many parts of your platform: one for the SaaS version, and one for the self-hosted version. Even if the code is physically the same (i.e. you provide some sort of easy to use wrapper for self-hosted installations), you still need to think about the differences.

1. https://yorickpeterse.com/articles/what-it-was-like-working-...

[ Parent | on HN ]