vert.x

The recent TechEmpower performance benchmarks have been showing vert.x on top of Netty, sometimes by a large amount. According to its website, vert.x uses Netty for "much of its network IO". If so, how does it achieve superior performance as compared to Netty? (Note: This is not intended to be controversial or flamebait - I really want to know the computer science reasons behind the performance difference. Thanks.) It depends which benchmark and which round you are talking about, rounds have different performant results and performance results are different for each benchmark (plaintext, json,

Vert.x is a tool-kit for building reactive applications on the JVM. I want to use vertx for JVM-based auto-scalable RESTful backend API. So far what I've found from the documentation, that it takes by default the number of cores in your machine, let's say you have N cores and creates N threads for each core, each thread is a event bus, each thread contains vertx instances. The question is, how does Vertx control the number of instances? based on load-pressure? This thing about control over the number of Verticles running withing a given thread i still don't get. Please help to clearify this

I'm developing in Vert.x (based on Netty and Hazelcast), and I'm trying to share data between two server instances (eache of those instances in different machines, on the same lan). My problem is that I don't know how to configure the vert.x servers to allow them to share their concurrent memory maps (the theory says that's possible). I've read many documents off Vert.x and Hazelcast but I haven't had results yet. (I don't know how to force vert.x to load hazelcast xml configuration files). Thanks in advance! There are options for sharing data among vertx instances on different machines Option

I have not done much in vert.x microservices, but I ran into the doubt of knowing the best way to communicate with each other miscroservices vert.x, using some middleware or web client, I do not know, or any other way that vert.x allows me. There's an infinite of possibilities to allow vert.x microservices to communicate between them, each with pros and cons and with more or less relevance depending on the context. Here is 3 common ways : 1) Using the native vert.x eventBus ( asynchronous logic) : https://vertx.io/docs/vertx-core/java/#event_bus (and you can use the Hazelcast Cluster Manager

while doing logs in the multiple module of vertx, it is a basic requirement that we should be able to correlate all the logs for a single request. as vertx being asynchronous what will be the best place to keep logid, conversationid, eventid. any solution or patterns we can implement? In a thread based system, you current context is held by the current thread, thus MDC or any ThreadLocal would do. In an actor based system such as Vertx, your context is the message, thus you have to add a correlation ID to every message you send. For any handler/callback you have to pass it as method argument

I am trying to use LoggerHandler to log all incoming requests. I am using logback.xml to specify appenders. I am setting system property for logging. System.setProperty("org.vertx.logger-delegate-factory-class-name", "org.vertx.java.core.logging.impl.SLF4JLogDelegateFactory"); Still it is logging everything in console not in file. This worked for me with Vert.x 3.4.1: import static io.vertx.core.logging.LoggerFactory.LOGGER_DELEGATE_FACTORY_CLASS_NAME; import io.vertx.core.logging.LoggerFactory; // ... setProperty (LOGGER_DELEGATE_FACTORY_CLASS_NAME, SLF4JLogDelegateFactory.class.getName ());