Vert.x 5 Roadmap

[vietj]

Vert.x 5 Roadmap

5.0.0

Development of Vert.x 5

• [x] Async result callback removals
• [x] Codegen improvements
  • [x] Modularization (Maven)
  • [x] Extract api in a vertx-codegen-api project
  • [x] Repackage vertx-codegen-processor classes in io.vertx.codegen.processor package
• [x] JDK 11 based build: Vert.x 5 should switch to JDK 11 as as minimum version, and builds/CI updated accordingly
  • [x] Vert.x pom parents allow deploy with JDK 11 for Vert.x 5
• [ ] Legacy Java feature cleanup: a couple of Java features are fading away with recent JDK versions, those should be migrated to replacement in Vert.x 5
  • [x] Java finalization
  • [ ] Biased locking
  • [ ] synchronized usage analysis to find un-necessary usage in particular with respect to biased locking
  • [ ] define biased locking removal strategies for each of the various usage
• [x] CLI cleanup: the Vert.x CLI will be removed from Vert.x 5 and the references to the CLI should be removed in Vert.x 4 as much as possible
  • [x] remove CLI usage in Vert.x examples (Vert.x 4 branch) https://github.com/vert-x3/vertx-examples/pull/450
  • [x] remove vertx-unit's CLI command https://github.com/vert-x3/vertx-unit/pull/77
  • [x] Implement Launcher equivalent with Picocli: Prototype
  • [x] Remove CLI usage in Vert.x Core (examples and code) https://github.com/eclipse-vertx/vert.x/pull/4769
  • [x] new repository in Vert.x 5 https://github.com/eclipse-vertx/vertx-launcher/pull/1
  • move the CLI framework to separate JAR (legacy)
  • integrate implementation with Picocli
  • [x] Udpate vertx-dependencies https://github.com/vert-x3/vertx-dependencies/pull/141
  • [x] vertx-stack CLI cleanup https://github.com/vert-x3/vertx-stack/pull/140
  • command part and deployment to central of the packaged zip
  • add new modules to the stack
  • [x] Vert.x Shell update (use the new JAR) https://github.com/vert-x3/vertx-shell/pull/55
  • [x] Website update https://github.com/vertx-web-site/vertx-web-site.github.io/pull/147
  • [x] Starter update (add vertx-application-launcher to Vert.x 5 projects)
  • [x] Implement redeployment in the Vert.x Maven Plugin
  • [x] Update deprecations and breaking changes doc
  • [x] Update Migration guide https://github.com/tsegismont/vertx-5-migration-guide/commit/78d3e4e82882a3ef43419b4d6b41dd3234b40e41
• [x] Undocumented system properties analysis and cleanup
• [ ] Core API improvements
  • [x] CompositeFuture methods should use generic Future<?> type instead of Future raw type
  • [x] Remove obsolete stream implementations (timer stream, request/connect/ws streams, UDP socket stream)
  • [x] Logging API removal, the internal logging API is preserved
  • [x] Replace HTTP client host/port properties by an authority property
  • [x] A few HTTP stream writeXXX API are fluent and instead should return a future signaling the success or failure of the write operation
  • [x] executeBlocking(Handler<Promise>) ➡ executeBlocking(Callable)
  • [x] Replace Future eventually function argument by a supplier argument
  • [x] Connect options / per connection SSL options
  • [x] ClientWebSocket
  • [x] HttpServerResponse close method removal
  • [x] Simplified lock API
  • [x] Vertx builder
  • [x] HTTP client builder
  • [x] Timer task as a Vert.x future
  • [x] Periodic task duplicates the context
  • [x] Local context data SPI
  • [x] Inbound read/message queue
  • [x] Outbound write/message queue
  • [x] TCP shutdown including WebSocket/HTTP
  • [x] Buffer fromJson/toJson
  • [x] ReadStream collector API
  • [x] Deployment API
  • [x] Future expectations
  • [x] HTTP response expectations
  • [x] HTTP client connection
  • HttpServerResponse#reset result should be asynchronous
  • HttpClientRequest#reset result should be asynchronous
  • WebsocketVersion ➡ WebSocketVersion
  • void start(Handler<Future<Void>>) ➡ Future<T> start()
  • WriteStream#write(...) returns a result extending Future allowing the result to signal back-pressure
  • avoids the write then writeQueueFull potentially racy (non event-loop) pattern
  • Future<T> should not extend anymore AsyncResult<T>
  • Remove SelfSignedCertificate that does not work after Java 8 du to JDK changes
  • Harmonize getter/setter naming convention across the API
  • Consider removing NoStackTraceThrowable https://github.com/eclipse-vertx/vert.x/issues/5012
  • [x] Integrate io_uring as a transport
• [ ] More data object conversion
  • [x] vertx-core
• [x] gRPC improvements
  • [x] JSON wire format
  • [x] gRPC Web
  • [x] Timeout and deadline
• [x] Service proxies improvements
  • [x] data object protobuf support
  • [x] protofile generation
• [ ] Usability improvements
  • [ ] Shared client configuration
  • [ ] Builders
  • [x] Builder style API guidelines
  • [x] Vertx builder
  • [x] HTTP client builder
  • [x] SQL client builder
  • [x] Builders for GraphQL handlers
  • [ ] Introduce dataobjects and or builders for Vert.x Web handlers
  • [x] Transform GraphiQL setup into subrouter creation
• [ ] RabbitMQ client
• [x] SQL client improvements
  • [x] remove Pool sub interfaces
  • [x] remove map of NetClient
  • [x] SqlConnectOptions should not extend anymore NetClientOptions
  • [x] remove Pool#connectionProvider that is replaced by Supplier<Future<SqlConnectOptions>>
  • [x] JDBC implementation use SQL common connection pool
  • [x] removal of deprecated legacy SQL client API
• [x] Micrometer
  • [x] Micrometer improvements
  • [x] Enable pool name tag by default
• [x] Service Discovery and load balancing for Vert.x clients
  • [x] Address resolver SPI
  • [x] Service discovery and load balancing integrating with address resolver SPI
  • [x] More load balancing policies https://github.com/eclipse-vertx/vert.x/issues/5154
  • [x] Random
  • [x] Power of two choices
  • [x] Hash based load-balancing (incl. sticky session) https://github.com/eclipse-vertx/vert.x/issues/5165
  • [x] Generic service lookup
• [x] Health checks dependencies cleanup
• [x] Circuit breaker improvements
• [x] Json Schema deprecated classes cleanup
  • [x] Update vertx-web
• [ ] Release process
• [x] Netty 4 decoupling
  • [x] Remove Netty from API usage
• [x] Infinispan 14 update
• [x] Hazelcast 5 update
• [x] Support request forwarding to Web API Service in OpenAPI Router
• [x] Context
  • [x] Resource segregation
  • [x] Event executor SPI
• [ ] JPMS support
  • [x] codegen split package removal
  • [x] vertx-codegen split package removal
  • [x] vertx-service-proxy
  • [x] vertx-sql-client
  • [x] vertx-rx
  • [x] vertx-lang-kotlin
  • [x] vertx-auth split package removal
  • [x] Netty JPMS support
  • [x] vertx-codegen JPMS support
  • [x] vertx-core JPMS preparation alternative 1
  • [x] vertx-core JPMS preparation alternative 2
  • [x] vertx-core JPMS support
  • [x] vertx-sql-client JPMS support
  • [x] vertx-jdbc-client JPMS support
  • [x] vertx-auth JPMS support
  • [x] vertx-uri-template JPMS support
  • [x] vertx-json-schema JPMS support
  • [x] vertx-openapi JPMS support
  • [x] vertx-service-resolver JPMS support
  • [x] vertx-grpc JPMS support
  • [x] vertx-http-proxy JPMS support
  • [x] vertx-grpc io.grpc decoupling
  • [x] vertx-redis-client JPMS support
  • [x] vertx-mail-client JPMS support
  • [x] vertx-cassandra-client JPMS support
  • [x] vertx-mongo-client JPMS support
  • [x] vertx-bridge-common
  • [x] vertx-web
  • [x] common + client
  • [x] other components
  • [x] vertx metrics
  • [x] vertx-dropwizard-metrics
  • [x] vertx-micrometer-metrics
  • [x] vertx-tracing
  • [ ] vertx-clustering
  • [x] vertx-hazelcast
  • [ ] others
  • [x] vertx-unit/junit
  • [x] vertx-jdbc-client
  • [x] vertx-mqtt
  • [x] vertx-stomp
  • [x] vertx-service-proxy
  • [x] vertx-proton
  • [x] vertx-amqp-client
  • [x] vertx-consul-client
  • [x] vertx-health-checks
  • [x] vertx-config
  • [x] vertx-circuit-breaker
  • [ ] cleanup / review assigned module names
• [x] Vert.x Tracing
  • [x] Use names specified by OpenTelemetry for tags
• [ ] Vertx Metrics
  • [ ] client metrics consistency and documentation
  • [x] redis
  • [x] sql client
  • [ ] ...
  • [x] metrics implementation should avoid specify a registry (micrometer) and instead it should be set on the vertx builder with a specific VertxMetricsFactory, deprecations in Vert.x 4.x should be applied
• [ ] Review Vert.x 5 backlog
• [ ] Release prep
  • [x] Ensure we use VerticleBase everywhere
  • [ ] Example improvements
  • [ ] Migration guide
  • [ ] Modular guide
  • [ ] Investigate GitHub dev container for how-to / example
  • [ ] Improve generation of release notes / breaking change
  • [ ] Blog post

5.x

• [ ] SQL client
  • [ ] possibly improve Query collector/mapping that are not composable
  • [ ] stored procedure API
  • [ ] HA support for PostgreSQL or more
• [ ] CouchDB client
• [ ] Non racy HTTP client methods when called outside event-loop
• [ ] HTTP/3
• [ ] Extra service resolver registry integration
• [ ] Core API improvements
  • [ ] Vertx shutdown / restart
• [ ] gRPC improvements
  • [ ] gRPC event bus bridge
• [ ] Service proxies improvements
  • [ ] service proxy using protobuf transport
  • [ ] service proxy streaming
  • [ ] #643

Components deprecation

• [ ] Service Discovery
• [ ] Vert.x gRPC Netty

Components sunset

• [ ] RxJava 1
• [x] Sync
• [x] Maven Service Factory
• [x] HTTP Service Factory
• [x] Service Factory
• [x] Docker base image generation

[hakarim740-com-ra]

Can we have support for HTTP/3?

[vietj]

it shall be implemented but most likely in 5.x, x > 0

[hakarim740-com-ra]

it shall be implemented but most likely in 5.x, x > 0

Can we get vertx.createQuicServer() or QuicServer.create(vertx) too?