Details

    • Type: New Feature
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects versions: 3.7.0
    • Fix versions: None
    • Components: None
    • Environment:

      Reactive Programming

    • Sprint:

      Description

      It would be great if we could use R2DBC as an execution engine which is the reactive alternative to JDBC.

      The motivation behind this ticket is that applications using reactive programming require non-blocking drivers for a SQL database integration. Although most Liquibase integrations run migrations during startup, a fully reactive application does not want to pull in JDBC drivers for the sole reason of bootstrapping and configure another integration but rather wants to reuse the already configured R2DBC connection.

      R2DBC is a specification initiative providing a standardized SPI for drivers and a vendor-independent interface similar to JDBC.

      Right now, the following drivers are available:

      • H2
      • Postgres
      • Microsoft SQL Server
      • MySQL
      • More to come

      Resources:

        Attachments

          Activity

            People

            • Reporter:
              mpaluch Mark Paluch
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: