Encapsulate Blocking Call the Reactor Way

• Use BlockHound to find blocking calls during testing
• Avoid Significant Work Before Subscribe
• Always look for async implementations
  • Encapsulate blocking calls
  • Find if a method is reactive

The one rule you aren’t allowed to break with project reactor is this: Don’t Block over Event Loop!

Event loops are main threads that shouldn’t be blocked.

If there is a blocking code, they should be run on a separate thread.

Here are some ways to fix these issues that I have noted down while watching Avoiding Reactor Meldown video. I have added an additional tip at the end.

Use BlockHound to find blocking calls during testing

BlockHound is a plugin provided by Project Reactor that helps find blocking calls.

If you are doing TDD, use junit version.

If you are aren’t doing TDD, use normal version but remove it in prod.

https://github.com/reactor/BlockHound

Remember that blockhound will only detect blocks on main thread. This means that if you are writing junit tests, if blocking call is not made on event loop, then it won’t be detected.

Avoid Significant Work Before Subscribe

Always look for async implementations

Completable futures can be converted to mono. Many java libraries have completable future implementations.

Encapsulate blocking calls

Find if a method is reactive