MDC for a Reactive Application
summary
Project Reactor's default MDC (Mapped Diagnostic Context) support only propagates metadata between reactive operators and doesn't cover calls inside those operators to third-party libraries. The talk presents an alternative MDC implementation developed by the presenter’s team that fully propagates context inside reactive applications (including inside operator-internal library calls) and removes the restriction that MDC values must be strings. It explains implementation details and the development path for this solution.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 6:02MDC with servlets and limits
- 12:04MDC problems in Reactor
- 22:28Solution: Reactor Context and storage
- 31:29Metadata fields and types
- 39:59Spring and Reactor 3.5+ update
- 41:03Summary
related talks
23mCorrelated Logs in Spring Apps with Reactive Parts
27mReactive: Understand and Embrace
45mShould I migrate to Reactive and how?
03mAm I only streaming? Thinking reactive
51mUnder the Hood of Reactive Data Access
24mEveryday Reactive
12mReactive architecture, design, and programming
42mReacting to the Future of Application Architecture