I'm not feeling the async pressure
IMHO all the rage on async comes from an era when interpreted languages where the main trend as they demonstrably increased developer productivity --I&#x27;m looking at you, Rails, Django.  Those platforms were not designed for runtime speed, so it made sense to push the bottleneck to the most inmediate backend system in the chain (i.e.: your trusty database, which is much faster than your agile framework of choice, remember the discussions of ORMs versus pure SQL?)<p>Then there came async frameworks a la Node, Twisted et al. and changed everything.  Again in my opinion, async code is harder to reason about versus synchronous code.<p>Things to keep in mind:<p>- Are you really working at scale?  Does the arguably added complexity of async benefit your particular use case?  Specially when SPA technologies allow to build simpler backend for frontend systems (pure API, no HTML rendering).  And not only regarding pure operational performance, Rails is still impossibly hard to beat when it comes to productivity.<p>- New players like Go, Rust have async capabilities but you dont necessarily need to use them to perform closer to native speed, hence becoming simpler solutions than Node, Ruby, or Python.  Guess that also applies to old dogs with new tricks in the JVM (Micronaut, Quarkus...)