Home Page Icon
Home Page
Table of Contents for
III. Building Reactive Applications and Systems with Quarkus
Close
III. Building Reactive Applications and Systems with Quarkus
by
Reactive Systems in Java
I. Reactive and Quarkus Introduction
1. Reactive in a nutshell
What do we mean by reactive?
Reactive software is not new!
The reactive landscape
Why are reactive architectures so well-suited for Cloud-native applications?
Reactive is not a silver bullet
2. Introduction to Quarkus
Java on the Cloud
Thorntail example
Quarkus example
The Quarkus Way
Create your first Quarkus application
Kubernetes with Quarkus in 10 minutes
Going native
Conclusion
II. Reactive and Event-Driven Applications
3. The Dark Side of Distributed Systems
What’s a Distributed System?
The new kids on the block: Cloud-Native and Kubernetes-Native applications
The dark side of distributed systems
The Fallacies of Distributed Computing in a Kubernetes World
A question of timing - The synchronous communication drawback
Summary
4. Design Principles of Reactive Systems
Reactive Systems 101
Commands and Events
Commands
Events
Messages
Commands vs. Events: an example
Destinations and Space Decoupling
Time-Decoupling
The role of non-blocking Input/Output (I/O)
Blocking Network I/O, threads and concurrency
How non-blocking I/O work?
Reactor pattern and event loop
Anatomy of reactive applications
Summary
5. Reactive Programming: Taming the Asynchronicity
Asynchronous code and patterns
Using Futures
Project Loom - Virtual Threads and Carrier Threads
Reactive Programming
Streams
Operators
Reactive programming libraries
Reactive Streams and the need for flow control
Buffering items
Dropping items
What is Back-Pressure?
Introducing reactive streams
Be warned; it’s a trap!
Back-pressure in a distributed systems
Summary
III. Building Reactive Applications and Systems with Quarkus
6. Quarkus - reactive engine
The imperative model
The reactive model
Unification of reactive and imperative
A reactive engine
A reactive programming model
Event-driven architecture with Quarkus
Summary
7. Mutiny - An event-driven reactive programming API
Why another reactive programming library?
What Makes Mutiny Unique?
Mutiny usage in Quarkus
Uni and Multi
Mutiny and Flow Control
Observing events
Transforming events
Chaining asynchronous actions
Recovering from failure
Combining and Joining items
Selecting items
Collecting items
Summary
8. HTTP with reactive in mind
The journey of an HTTP request
Say Hello to RESTEasy Reactive!
So, What’s the benefit?
Asynchronous endpoints returning Uni
Dealing with failure and customizing the response
Streaming data
Raw streaming
Streaming JSON Array
Using Server-Sent-Event
Reactive Score
Summary
9. Accessing data reactively
The problem with data access
Non-blocking interactions with relational database
Using a reactive ORM: Hibernate Reactive
What about noSQL?
Interacting with Redis
Data related events and change data capture
Using Debezium to capture change
Summary
Index
Search in book...
Toggle Font Controls
Playlists
Add To
Create new playlist
Name your new playlist
Playlist description (optional)
Cancel
Create playlist
Sign In
Email address
Password
Forgot Password?
Create account
Login
or
Continue with Facebook
Continue with Google
Sign Up
Full Name
Email address
Confirm Email Address
Password
Login
Create account
or
Continue with Facebook
Continue with Google
Prev
Previous Chapter
5. Reactive Programming: Taming the Asynchronicity
Next
Next Chapter
6. Quarkus - reactive engine
Part III.
Building Reactive Applications and Systems with Quarkus
Add Highlight
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click
here
login for view all page.
Day Mode
Cloud Mode
Night Mode
Reset
