Reactive vs. Traditional Models
Jürgen discusses when to adopt a reactive web interaction model, emphasizing that if the bottleneck lies within database interactions, sticking to traditional Spring MVC may be more beneficial. He highlights the importance of a cohesive architecture throughout the application and addresses the challenges of implementing non-blocking JDBC in relational databases, noting that the reactive demands must align with the database's capabilities.In this clip
From this podcast
Software Engineering Radio - the podcast for professional software developers
SE-Radio-Episode-267-Jürgen-Höller-on-Reactive-Spring-and-Spring-5.0
Related Questions