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 14. Concurrencia en la JVM
Este trabajo se ha traducido utilizando IA. Agradecemos tus opiniones y comentarios: translation-feedback@oreilly.com
Mario Fusco
Originalmente, los hilos sin procesar eran el único modelo de concurrencia disponible en la JVM, y siguen siendo la opción por defecto para escribir programas paralelos y concurrentes en Java. Sin embargo, cuando se diseñó Java hace 25 años, el hardware era radicalmente distinto. La demanda de ejecución de aplicaciones paralelas era menor, y las ventajas de la concurrencia estaban limitadas por la falta de procesadores multinúcleo: las tareas podían desacoplarse, pero no ejecutarse simultáneamente.
Hoy en día, la disponibilidad y la expectativa de la paralelización han dejado claras las limitaciones del multihilo explícito. Los hilos y los bloqueos son de nivel demasiado bajo: utilizarlos correctamente es difícil; comprender el Modelo de Memoria Java, aún más. Los subprocesos que se comunican a través de un estado mutable compartido no son aptos para el paralelismo masivo, pues dan lugar a sorpresas no deterministas cuando el acceso no está bien sincronizado. Además, aunque tus bloqueos estén dispuestos correctamente, el propósito de un bloqueo es restringir los hilos que se ejecutan en paralelo, reduciendo así el grado de paralelismo de tu aplicación.
Como Java no admite memoria distribuida, es imposible escalar horizontalmente ...
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.