Last year right in the middle of SpringOne Platform 2018, I posted the first post in this series, _ The Reactive Revolution at SpringOne Platform 2018 (part 1/N)_, which looked at some of the big features we’d just dropped at SpringOne Platform 2018. I wanted to follow up and revisit that blog and the concepts I’d introduced last year, and show just how far we’ve come in the intervening year. TL;DR: things are much easier!
Last year, we announced our work on trying to support a standard for reactive SQL data access with a new project called R2DBC. Traditional approaches to SQL data access on the JVM, like JDBC, are blocking APIs. They monopolize threads to do their work and negate the scalability benefits of a reactive platform like Spring. We wanted to improve that situation for developers so we built R2DBC. R2DBC has now been out in the public for more than a year and was developed internally for about as long internally before that. We’ve just reached the 0.0.8 release. We’re nearing a GA release. I’m not sure when, but I reckon we’ll have a majority of the features most developers need in a possibly GA, but-not-yet-1.0, release. Things like stored procedures might be released later.