One of the most common ways to fail when using Project Reactor is to block a thread meant to handle only nonblocking tasks. This talk covers practices for detecting and avoiding such a reactor meltdown.
Specifically, the talk covers architecture-level and service-level practices for isolating blocking calls, coding guidelines to decrease the chance of introducing a blocking bug, code smells and red flags to look for in code reviews, and tools to help detect incorrect blocking at runtime (e.g., BlockHound).
We'll show code examples of blocking problems and solutions, as well as a live demo with BlockHound.
Speaker: Phil Clay, Principal Software Engineer, Blizzard Entertainment
Filmed at SpringOne Platform 2019
SlideShare: www.slideshare.net/SpringCent...
1 авг 2024
