Hacker News Reader

Alternatively, you can use a message queue or a REST service, and whatever lightweight, async database frontend.

That would just move the blocking code elsewhere, and now you have one extra framework / message queue on your stack (free complexity)

The point is to use a non-blocking DB frontend. Not necessarily JVM-based.