August 2024
Intermediate to advanced
616 pages
22h 8m
Spanish
Content preview from Diseño de aplicaciones intensivas en datos
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
Capítulo 9. Coherencia y consenso
Este trabajo se ha traducido utilizando IA. Agradecemos tus opiniones y comentarios: translation-feedback@oreilly.com
¿Es mejor estar vivo y equivocado o estar bien y muerto?
Jay Kreps, Algunas notas sobre Kafka y Jepsen (2013)
En los sistemas distribuidos pueden fallar muchas cosas, como se explica en el Capítulo 8. La forma más sencilla de tratar estos fallos es simplemente dejar que falle todo el servicio y mostrar al usuario un mensaje de error. Si esa solución es inaceptable, tenemos que encontrar formas de tolerar los fallos, es decir, de mantener el servicio funcionando correctamente, aunque algún componente interno esté defectuoso.
En este capítulo, hablaremos de algunos ejemplos de algoritmos y protocolos para construir sistemas distribuidos tolerantes a fallos. Supondremos que pueden ocurrir todos los problemas del Capítulo 8: los paquetes pueden perderse, reordenarse, duplicarse o retrasarse arbitrariamente en la red; los relojes son aproximados en el mejor de los casos; y los nodos pueden hacer una pausa (por ejemplo, debido a la recogida de basura) o bloquearse en cualquier momento.
La mejor forma de construir sistemas tolerantes a fallos es encontrar algunas abstracciones de propósito general con garantías útiles, implementarlas una vez, y luego dejar que las aplicaciones confíen en esas garantías. Este es el mismo enfoque que ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.