Nouveauté
System Design in One Easy Piece: Amazon Dynamo. System Design in One Easy Piece, #1
Par :Formats :
Disponible dans votre compte client Decitre ou Furet du Nord dès validation de votre commande. Le format ePub est :
- Compatible avec une lecture sur My Vivlio (smartphone, tablette, ordinateur)
- Compatible avec une lecture sur liseuses Vivlio
- Pour les liseuses autres que Vivlio, vous devez utiliser le logiciel Adobe Digital Edition. Non compatible avec la lecture sur les liseuses Kindle, Remarkable et Sony
, qui est-ce ?Notre partenaire de plateforme de lecture numérique où vous retrouverez l'ensemble de vos ebooks gratuitement
Pour en savoir plus sur nos ebooks, consultez notre aide en ligne ici
C'est si simple ! Lisez votre ebook avec l'app Vivlio sur votre tablette, mobile ou ordinateur :
- FormatePub
- ISBN8996765409
- EAN9798996765409
- Date de parution23/06/2026
- Protection num.pas de protection
- Infos supplémentairesepub
- ÉditeurSystems Potpourri LLC
Résumé
The Amazon Dynamo paper changed how the industry thinks about scale. It proved you could choose availability over strict consistency and still run a billion-dollar storefront - but the distance between that landmark academic paper and production-ready code has stopped countless engineers cold. System Design in One Easy Piece is built to close that gap. Volume 1 takes a single landmark system - Amazon's Dynamo (DeCandia et al., SOSP 2007) - and deconstructs it from first principles, one decision at a time.
Starting from a deceptively simple question - how do you keep a shopping cart always writable? - it builds the entire architecture in front of you: consistent hashing and the ring, virtual nodes, gossip-based membership, replication and preference lists, quorums (N, R, W), sloppy quorums and hinted handoff, anti-entropy with Merkle trees, version vectors for conflict resolution, and the tail-latency optimizations that make it production-grade.
A closing capstone challenges you to assemble the whole system yourself. Written for working software engineers, it sits deliberately between the academic and the practical: rigorous enough to ground every claim in the original paper, concrete enough to use on Monday. Whether you're preparing for a senior system-design interview or designing the next distributed database, this is the blueprint.
Starting from a deceptively simple question - how do you keep a shopping cart always writable? - it builds the entire architecture in front of you: consistent hashing and the ring, virtual nodes, gossip-based membership, replication and preference lists, quorums (N, R, W), sloppy quorums and hinted handoff, anti-entropy with Merkle trees, version vectors for conflict resolution, and the tail-latency optimizations that make it production-grade.
A closing capstone challenges you to assemble the whole system yourself. Written for working software engineers, it sits deliberately between the academic and the practical: rigorous enough to ground every claim in the original paper, concrete enough to use on Monday. Whether you're preparing for a senior system-design interview or designing the next distributed database, this is the blueprint.