You’ll often hear about the CAP theorem which specifies some kind of an upper limit when designing distributed systems. As with most of my other introduction tutorials, lets try understanding CAP by comparing it with a real world situation.
Chapter 1: “Remembrance Inc” Your new venture :
Last night when your spouse appreciated you on remembering her birthday and bringing her a gift, a strange Idea strikes you. People are so bad in remembering things. And you’re sooo good at it. So why not start a venture that will put your talent to use? The more you think about it, the more you like it. In fact you even come up with a news paper ad which explains your idea
Remembrance Inc! - Never forget, even without remembering!
Ever felt bad that you forget so much? Don't worry. Help is just a phone away!
When you need to remember something, just call 555--55-REMEM and tell us what you need to remember. For eg., call us and let us know of your boss's phone number, and forget to remember it. when you need to know it back.. call back the same number[(555)--55-REMEM ] and we'll tell you what's your boss's phone number.
Charges : only $0.1 per request
So, your typical phone conversation will look like this:
- Customer : Hey, Can you store my neighbor’s birthday?
- You: Sure.. when is it?
- Customer : 2nd of jan
- You: (write it down against the customer’s page in your paper note book )Stored. Call us any time for knowing your neighbor’s birthday again!
- Customer : Thank you!
- You: No problem! We charged your credit card with $0.1
A Few months later…
- Customer : Hey , can you tell me when is my neighbor’s birthday?
- You: 1 sec please..
- You: Thank you for holding. It’s 2nd of jan sir.
- Customer : Thank you!
- You: No problem! We Charged your credit card with $0.1
(look up the customer’s page in your note book)
