Skip to content
Snippets Groups Projects

Document Google Spanner for Global Service

Merged Steve Xuereb requested to merge cells-global-service-spanner into cells-global-service
2 unresolved threads

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.

Edited by Steve Xuereb

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
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.
Please register or sign in to reply
Loading