R2DBC was officially incubated successfully, which is good for Spring Webflux

On April 25, 2022, the R2DBC community announced the official release of 1.0.0.RELEASE with general availability.

R2DBC is committed to bringing specification support for the reactive programming API to operate relational databases. Unlike the well-known JDBC specification, R2DBC is asynchronous and reactive.

After 5 years of community efforts and 268 votes, R2DBC has finally reached a state where it can release 1.0 . After the incubation and verification of the 0.8 and 0.9 versions, the community has confirmed that R2DBC is moving in the right direction of the reliable database connection specification.

Among other features, the specification includes the following highlighted features:

• Drivers SPI and TCK (Technology Compatibility Kit)
• Integrated BLOB and CLOB types
• Extensible Transaction Definition
• Plain Statements and Parameterized Statements ("Prepared Statements")
• Support stored procedure/server side IN and OUT parameter binding execution function
• Data update count, record row count, and consumption statistics for stored procedure results
• Bulk operations
• Classifiable Operational Exceptions
• Driver discovery based on ServiceLoader
• New database connection URL scheme
• Programmable configuration API

Starting from 1.0 , R2DBC will no longer release a train-type BOM like Spring Cloud for developers to choose the appropriate suite according to their needs. Database vendors and specification implementers will independently maintain drivers based on the R2DBC specification at their own pace. , the focus of the community will be on a maintenance iteration of the R2DBC specification. Version 1.0 defines the stable state for the foreseeable future, and database driver vendors are expected to all upgrade to R2DBC 1.0 this year.

For more information and practical operations about R2DBC, you can refer to Fat Brother's previous blog posts.

关注公众号：Felordcn 获取更多资讯

Personal blog: https://felord.cn