diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-10-18 12:08:09 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-10-18 12:08:09 +0300 |
| commit | 990891feb7cb31269ad7ec13f359aea6b25c1f00 (patch) | |
| tree | 0c1dba50660232fc0d9c1e37ea3e96783abca718 /doc/development | |
| parent | ccf350cb4cab8bcaa457313fea2d596d50cdf820 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development')
| -rw-r--r-- | doc/development/database/multiple_databases.md | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/development/database/multiple_databases.md b/doc/development/database/multiple_databases.md index d6f14c82f33..79e1d3c0578 100644 --- a/doc/development/database/multiple_databases.md +++ b/doc/development/database/multiple_databases.md @@ -47,6 +47,13 @@ The usage of schema enforces the base class to be used: - `Gitlab::Database::SharedModel` for `gitlab_shared` - `PackageMetadata::ApplicationRecord` for `gitlab_pm` +### Guidelines on choosing between `gitlab_main_cell` and `gitlab_main_clusterwide` schema + +When you choose the appropriate schema for tables, consider the following guidelines as part of the [Cells](../../architecture/blueprints/cells/index.md) architecture: + +- Default to `gitlab_main_cell`: We expect most tables to be assigned to the `gitlab_main_cell` schema by default. Choose this schema if the data in the table is related to `projects` or `namespaces`. +- Consult with the Tenant Scale group: If you believe that the `gitlab_main_clusterwide` schema is more suitable for a table, seek approval from the Tenant Scale group This is crucial because it has scaling implications and may require reconsideration of the schema choice. + ### The impact of `gitlab_schema` The usage of `gitlab_schema` has a significant impact on the application. |