search

nelson-yeh-fy / Adventure

0 stars 0 forks source link

basics#2 - CAP Theorem #40

Open sync-by-unito[bot] opened 3 years ago

sync-by-unito[bot] commented 3 years ago

Note to bush up system design basics#2 - CAP Theorem:

It's prudent to understand how your system will fail to meet either C or A (while having scaling in mind) Every failure of availability means lost money. (The choice of availability over consistency is usually a business choice, not a technical one).

Have I 'beaten' the CAP theorem? No. Design a system that is not heavily affected by it, is good. That's why we have "eventual consistency" and other patterns. because Everything is a trade-off. (Asking questions and do requirements elicitation is a must)

┆Issue is synchronized with this Trello card by Unito ┆Attachments: Trade-offs: Google's transactions across datacenters (AP) | Trade-offs: Google's transactions across datacenters (AP)

sync-by-unito[bot] commented 3 years ago

➤ Nelson 3513 commented:

Trade-offs: Google's transactions across datacenters (AP) https://www.youtube.com/watch?v=srOgpXECblk https://snarfed.org/transactions_across_datacenters_io.html

sync-by-unito[bot] commented 3 years ago

➤ Nelson 3513 commented:

Trade-offs: Google's transactions across datacenters 106945492_10217934527498935_8234341085020921936_n.jpg ( https://trello-attachments.s3.amazonaws.com/5f1e4f876a5b017435b16478/5f20cf25ea56034118270692/0e64d4a87420668ffcc2520be7d18163/106945492_10217934527498935_8234341085020921936_n.jpg )