I’ve been working on an independent R2DBC driver for Microsoft SQL Server (not a fork of the official one). It’s public-domain, implements the R2DBC SPI, and speaks TDS using only the JDK (no Netty).

The main reason I started it was better control over FedAuth / Azure AD / Windows Authentication flows in a reactive stack. I hit enough friction with existing options that it seemed worth doing a clean implementation.

A few things I’m particularly interested in feedback on:

How the pure-JDK TDS approach compares to Netty-based ones for typical workloads

Edge cases or gotchas people have seen with FedAuth / Azure AD token handling in reactive clients

Whether the public-domain licensing is actually useful for anyone, or mostly irrelevant

Maven coordinates if anyone wants to try it:

org.mssqllib.r2dbc.mssql:r2dbc-mssql:1.0.0

Site: mssqllib.org

Curious what others have run into with reactive SQL Server clients, or if there are specific protocol/auth areas worth focusing on next.…