Book Image

Java 9 Concurrency Cookbook, Second Edition - Second Edition

By : Javier Fernández González
Book Image

Java 9 Concurrency Cookbook, Second Edition - Second Edition

By: Javier Fernández González

Overview of this book

Writing concurrent and parallel programming applications is an integral skill for any Java programmer. Java 9 comes with a host of fantastic features, including significant performance improvements and new APIs. This book will take you through all the new APIs, showing you how to build parallel and multi-threaded applications. The book covers all the elements of the Java Concurrency API, with essential recipes that will help you take advantage of the exciting new capabilities. You will learn how to use parallel and reactive streams to process massive data sets. Next, you will move on to create streams and use all their intermediate and terminal operations to process big collections of data in a parallel and functional way. Further, you’ll discover a whole range of recipes for almost everything, such as thread management, synchronization, executors, parallel and reactive streams, and many more. At the end of the book, you will learn how to obtain information about the status of some of the most useful components of the Java Concurrency API and how to test concurrent applications using different tools.
Table of Contents (12 chapters)

Reactive programming with reactive streams

Reactive streams (http://www.reactive-streams.org/) define a mechanism to provide asynchronous stream processing with non-blocking back pressure.

Reactive streams are based on the following three elements:

  • A publisher of information
  • One or more subscribers of that information
  • A subscription between the publisher and a consumer

The reactive streams specification determines how these classes should interact among them, according to the following rules:

  • The publisher will add the subscribers that want to be notified
  • The subscriber receives a notification when they're added to a publisher
  • The subscribers request one or more elements from the publisher in an asynchronous way, that is to say, the subscriber requests the element and continues with the execution
  • When the publisher has an element to publish, it sends it to all its subscribers that have requested an element...