-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate to vertx version 4 #22
Comments
yes indeed - this has to be done. @deedarb - feel free to contribute. |
i've seen hazelcast, infinispan implementation for vertx 4. |
@vietj could you help me with understanding clusterHost & clusterPublicHost, if i understand correctly vertx instance will not start consul agent so i should not override clusterHost? |
Tagging @tsegismont for his input here. |
@deedarb some cloud providers have network configurations that make you bind server sockets to a hostname that is not the name used by others to reach you from the outside (for security reasons). Vert.x needs to know which hostname (cluster host) to use when binding the eventbus server socket. It also needs to know which hostname (public host) it should advertise to other Vert.x nodes. |
There is some update for this task? |
@robertonav20 I stopped migrating, planning to switch to quarkus + stork |
No description provided.
The text was updated successfully, but these errors were encountered: