Almost every Spring WebFlux example out there is leveraging Spring Data MongoDB to build Reactive end to end solutions.
As I understand it,
JDBC is inherently a blocking API and we'll not be getting reactive support for relational databases any time soon. Leveraging Spring JPA async queries and dedicated
thread pools can potentially improve things but it is not a replacement for real Reactive support.
My question is. Ate there known limitations when using Spring WebFlux with a "blocking" persistence layer such as a Spring Data JPA? Would it even make sense to build a Reactive REST API on top of a traditional blocking persistence layer (in terms os scalability)?