October 2024
Intermediate to advanced
270 pages
8h 13m
Spanish
Content preview from 97 cosas que todo programador Java debe saber
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 84. Compromisos en una arquitectura de microservicios
Este trabajo se ha traducido utilizando IA. Agradecemos tus opiniones y comentarios: translation-feedback@oreilly.com
Kenny Bastani
¿Existe una arquitectura de software óptima? ¿Qué aspecto tiene? ¿Cómo medimos lo "óptimo" cuando se trata de construir y utilizar software? Una arquitectura de software óptima es la que tiene la máxima flexibilidad para el cambio al menor coste posible. Aquí, el coste se mide en términos de ciertas cualidades que representan el diseño y la implementación de una arquitectura de software, además del coste de la infraestructura para hacerla funcionar. El rasgo definitorio de una cualidad del software es que puede medirse de forma tangible y repercute en otras cualidades.
Por ejemplo, si una arquitectura de software requiere fuertes garantías de consistencia, se produce un impacto en cualidades como el rendimiento y la disponibilidad. Eric Brewer creó el teorema CAP para describir un conjunto de compensaciones medibles en las que sólo puedes elegir dos de las tres garantías de para ejecutar una base de datos: consistencia, disponibilidad y tolerancia a la partición. El teorema afirma que cuando las aplicaciones comparten estado a través de los límites de una red, debes elegir entre consistencia o disponibilidad, pero no puedes tener ambas.
Uno de los principales problemas de los microservicios ...
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.