Uploaded image for project: 'AMQ Streams'
  1. AMQ Streams
  2. ENTMQST-4360

Move from Vert.x to Quarkus

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • 2.2.0.GA
    • kafka-bridge
    • None

      Currently, the bridge is leveraging a number of Vert.x components in order to get the HTTP endpoints from an OpenAPI specification, exposing them at runtime and handling the requests coming from the clients.

      The referred components are:

      • vertx-web (with its dependencies vertx-auth-common and vertx-bridge-common)
      • vertx-web-common
      • vertx-web-openapi
      • vertx-web-validation
      • vertx-json-schema

      We should get rid of those components and find a different way to allow the bridge to get endpoints from an OpenAPI specification as well as handling incoming HTTP requests taking the good or having better performance, if possible, than today.

              ppatiern Paolo Patierno
              ppatiern Paolo Patierno
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: