What problem does it solve? Adding a reactive MariaDB driver to a Java build is error-prone because the R2DBC connector differs from the JDBC driver in artifact coordinates, URL scheme, connection factory wiring, pooling, and TLS defaults, and common assumptions carried over from JDBC silently break the setup. ## Core Features & Use Cases - Build Integration: Provides the correct Maven and Gradle coordinates for org.mariadb:r2dbc-mariadb plus the separate io.r2dbc:r2dbc-pool dependency needed for connection pooling. - ConnectionFactory Configuration: Shows URL-based (r2dbc:mariadb://) and programmatic MariadbConnectionConfiguration setup, including Unix socket connections and parameter names that differ from JDBC (username, socket). - TLS and Pooling Setup: Explains that sslMode defaults to DISABLE, how to enable VERIFY_FULL with serverSslCert, how to disable system truststore fallback, and how to wrap a factory in an R2DBC ConnectionPool. - Use Case: A developer building a Spring Data R2DBC service adds the driver, wires a ConnectionFactory with mutual TLS, and configures a 20-connection pool without falling into JDBC-driver traps like DriverManager or jdbc: URLs. ## Quick Start Ask the AI to add the MariaDB R2DBC driver to your Maven or Gradle build and configure a pooled, TLS-enabled ConnectionFactory for your database host.