Reactive and Imperative Context Propagation in Spring Applications by Dariusz Jędrzejczyk
Applications have relied on contextual data that is outside of core business logic for a long time to provide vital insight into what the application is doing. Traditionally, Java applications built on the ThreadLocal construct to aggregate meta and observability information. With the introduction of asynchrony to the processing, it became easy to lose the precious, contextual data. After providing the background behind current design and implementation of context support in Project Reactor, we’ll move to practical aspects that Spring application developers face. We’ll introduce a new Context Propagation library under Micrometer, which provides new and essential capabilities for bridging reactive and imperative programming styles. Reactor 3.5 has dedicated support for interacting with these concepts. Next, we’ll cover how Reactor uses Micrometer 1.10’s Observation feature to provide metrics, tracing, and logging and how library implementers can take advantage of these patterns.

Do’s and Don’ts: Avoiding First-Time Reactive Programmer Mines

Micrometer Mastery: Unleash Advanced Observability In Your JVM Apps (SpringOne 2024)

Correlated Logs in Spring Apps with Reactive Parts

How to Escape the Legacy Trap: A Proven Strategy for Application Modernization

Keynote: Introducing Spring Framework 6

The Talking Application: Giving Your Spring Applications a Voice with Alexa

Guide to "Reactive" for Spring MVC Developers

How to Avoid Common Mistakes When Using Reactor Netty

Avoiding Reactor Meltdown

Spring Office Hours: S5E16 - May Release Train Shift & What's Coming in Spring Boot 4.1

From Imperative To Reactive Web Apps

Reactive Relational Database Connectivity with Spring

Demystifying Spring Internals

Introducing Micrometer Application Metrics - Jon Schneider

Introduction to Spring Cloud

The Golden Path to SpringOne: What’s new with VMware Tanzu Application Service with Nick Kuhn

