Vert.x is a very efficient framework, and because of the asynchronous nature of Vert.x code, performance bottlenecks are much more likely to crop up in databases or other dependent systems. When you do need to scale the Vert.x application itself, the following techniques are available.
In Chapter 5, Polyglot Development and Modules, when deploying the
svg2png worker verticle, we deployed three instances of it. This is similar to setting up three concurrent worker threads for processing a task in a more traditional system. At most three instances of the same job can be running concurrently.
The same scaling technique is also available for non-worker verticles. For any verticle, we can specify the number ...