Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • S system-design-primer
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 173
    • Issues 173
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 190
    • Merge requests 190
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Donne Martin
  • system-design-primer
  • Merge requests
  • !297

Added detail on CAP theorem limitations

  • Review changes

  • Download
  • Email patches
  • Plain diff
Open Administrator requested to merge github/fork/chris838/master into master Jun 30, 2019
  • Overview 2
  • Commits 1
  • Pipelines 0
  • Changes 1

Created by: chris838

I thought this blog post from Martin Kleppman (https://martin.kleppmann.com/2015/05/11/please-stop-calling-databases-cp-or-ap.html) was super interesting and helps explain what we actually mean by consistency and availability, which is not what the CAP theorem meant in its original form. I've added the link and included a single paragraph that summarises his key point. Hopefully, this is useful for other readers too!

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: github/fork/chris838/master