CAP and you
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

CAP and you

on

  • 3,149 views

CAP theorem is simple if we all use the same definitions. CAP follows from the requirements for nodes in distributed systems to send and receive messages before responding if the system requires ...

CAP theorem is simple if we all use the same definitions. CAP follows from the requirements for nodes in distributed systems to send and receive messages before responding if the system requires atomic consistency. If the system can't pass messages, it can't be consistent. If consistency is a requirement, then losing messages implies the system cannot respond.

These properties apply to any distributed systems.

Statistics

Views

Total Views
3,149
Views on SlideShare
3,135
Embed Views
14

Actions

Likes
0
Downloads
39
Comments
1

5 Embeds 14

http://blog.mccrory.me 6
https://twitter.com 3
http://www.linkedin.com 2
https://www.linkedin.com 2
https://si0.twimg.com 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

CC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
  • Is there a recording of the live talk anywhere (I can't find one)? Would love to hear more about slide 18, which you also commented on in a recent DevOps Cafe podcast.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

CAP and you Presentation Transcript

  • 1. Consistency…Availability…Messages…& You…
  • 2. CAPtheorem
  • 3. Consistent
    ACID Compliant
    “…as if every request was executing on a single node, responding to operations one at a time.”
  • 4. Available
    “…every request received by a non-failing node in the system must result in a response.”
  • 5. Partition Tolerant
    “…the network will be allowed to lose arbitrarily many messages sent from one node to another”
  • 6. Pick Any Two!?!!
    It’s complicated…
  • 7. Consistent & Partition Tolerant
    “…it is easy to achieve atomic data and partition tolerance. The trivial system that ignores all requests meets these requirements.”
  • 8. Consistent & Available
    “If there are no partitions, it is clearly possible to provide atomic, available data.”
  • 9. Available & Partition Tolerant
    “If there are no consistency requirements, the service can trivially return v0, the initial value, in response to every request.”
  • 10. t-Connected Consistent
  • 11. What has been neglected?
    • Latency
    • 12. Failure
    • 13. Computation
    • 14. Durability
    • 15. More™
  • Latency
    Petite Partitions
    the little deaths
  • 16. When the available consistency exceeds the required availability a choice must be made…
  • 17. Raising the question, how are business decisions made?
  • 18.
  • 19. What protocols are used to pass messages in your organization?
  • 20.
  • 21. Has your organization chosen consistent, available or partition tolerant?
  • 22. In any human interaction, the required amount of communication is inversely proportional to the level of trust…
    @bhorowitz
  • 23. Andrew Clay Shafer
    @littleidea
    work on stuff that matters