Good question, great you like Vert.x. If it fits your requirements it is the ...

Niklas Lochschmidt Oct 9, 2017

Follow

Good question, great you like Vert.x. If it fits your requirements it is the right tool for you. I have briefly tried out Vert.x Web and thought it’s great that it aims for complete event-driven and asynchronous handling of requests down to the database, external services, message queues, etc. That makes it quite a bit different from the still typical style of development. That said, Jooby also has support for this kind of reactive programming (see rxjdbc), however I didn’t try it yet. With Vert.x, I did struggle a lot at writing unit tests for the API layer and didn’t find good sources of information on how to do that properly. What is your approach there, if I may ask? Do you have a good example project? With regards to speed, it is my opinion that the raw performance of the framework itself is often far less important then the performance of underlying libraries that deal with JSON parsing or database connection handling just to name two of them. Those will likely be the same between projects anyways and I like it that the layer around these common libraries is particularly thin in Jooby. Lastly, in my projects, the speed with which I can develop is often as important as the performance of the service. It obviously depends on the specific requirements of the project at hand.