Document Google Spanner for Global Service
What does this MR do and why?
What
Add a new section in the Global Service blueprint about Google Spanner
Why
We only looked at Spanner briefly, so we needed to do more research on the platform.
Reference: #454056 (closed)
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Merge request reports
Activity
assigned to @sxuereb
mentioned in issue Taucher2003/reporting#423 (closed)
- Resolved by 🤖 GitLab Bot 🤖
Proper labels assigned to this merge request. Please ignore me.
@sxuereb - please see the following guidance and update this merge request.1 Error Please add typebug typefeature, or typemaintenance label to this merge request. Edited by 🤖 GitLab Bot 🤖
added maintenancerefactor typemaintenance labels
added docs-only label
- A deleted user
added Architecture Evolution Blueprint documentation labels
2 Warnings 44a10828: The commit body should not contain more than 72 characters per line. For more information, take a look at our Commit message guidelines. This merge request does not refer to an existing milestone. 2 Messages This merge request might require a review from a Coach Engineer. This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge. Architecture Evolution Review
This merge request might require a review from a Coach Engineer.
Following files, that may require the additional review, have been changed:
doc/architecture/blueprints/cells/global-service.md
Documentation review
The following files require a review from a technical writer:
-
doc/architecture/blueprints/cells/global-service.md
(Link to current live version)
The review does not need to block merging this merge request. See the:
-
Metadata for the
*.md
files that you've changed. The first few lines of each*.md
file identify the stage and group most closely associated with your docs change. - The Technical Writer assigned for that stage and group.
- Documentation workflows for information on when to assign a merge request for review.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
Dangermentioned in merge request !145944 (merged)
@ayufan mind if you take a look?
@alexander-sosna I would also appreciate your input on this since it's a brand new datastore. This merge request is built on top of !145944 (merged) which might be useful for context.
requested review from @ayufan and @alexander-sosna
mentioned in issue #454056 (closed)
removed maintenancerefactor label
added typefeature label and removed typemaintenance label
mentioned in merge request !148382 (merged)
@ayufan this should be ready for another round of review. I've merged !148382 (merged) into it as well.
mentioned in commit 452d29ef
changed milestone to %16.11
180 182 additional functions. 181 183 184 ## Spanner 185 186 [Spanner](https://cloud.google.com/spanner) will be a new data store introduced into the GitLab Stack, the reasons we are going with Spanner are: 187 188 1. It supports Multi-Regional read-write access with a lot less operations when compared to PostgreSQL helping with out [regional DR](../disaster_recovery/index.md) 189 1. The data is read heavy not write heavy. 190 1. Spanner provides [99.999%](https://cloud.google.com/spanner/sla) SLA when using Multi-Regional deployments. 191 1. Provides consistency whilst still being globally distributed. 192 1. Shards/[Splits](https://cloud.google.com/spanner/docs/schema-and-data-model#database-splits) are handled for us. 193 194 The cons of using Spanners are: 195 196 1. Vendor lock-in, our data will be hosted in a proprietary data. 197 - How to prevent this: Global Service will use generic SQL.