R2DBC should allow URL-based configuration as this mechanism has proved to be useful for a lot of data access technologies (JDBC, MongoDB, Redis, …).
URL-based configuration makes it very convenient to configure a driver as it carries already significant details about the connection endpoint, protocol, and potential, additional options.

R2DBC SPI should provide a basic URL specification and parsing implementation to parse R2DBC URL's into ConnectionFactoryOptions.

API to be added

• Add static parse(String) and parse(URI) methods to ConnectionFactoryOptions returning ConnectionFactoryOptions. This method implements parsing.
• Add static get(String) method to ConnectionFactories returning ConnectionFactory as shortcut for drivers. This method invokes parsing and get(ConnectionFactoryOptions).

We should also document the URL configuration behavior within the spec documentation.

See also

• Proposal at mailing list: https://groups.google.com/forum/#!topic/r2dbc/_dswx51XoDU