also some of the points that was compelling for trying qurakus were :
support for reactive hibernate : which is a fork of the famous ORM that uses mysql and postgres reactive drivers, this means a total reactive io stack , from handling the api calls to calling the database.
support for vert.x :
Vert.x uses some hybrid model that uses both node-like event loop , separate threads if needed , and an actor-model like event messaging system.
This should mean even more squeezed performance while avoiding the cons of event-loops in high computation tasks, because you can easily switch to using a dedicated thread for those.
The internal messaging system can be used for decoupling services and easily separating them later if needed, and also provides implicit concurrency like the actor model.
Quarkus provides a layer over vert.x , making working with it easier and integrate it to the application under the hood.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
also some of the points that was compelling for trying qurakus were :
support for reactive hibernate : which is a fork of the famous ORM that uses mysql and postgres reactive drivers, this means a total reactive io stack , from handling the api calls to calling the database.
support for vert.x :
Vert.x uses some hybrid model that uses both node-like event loop , separate threads if needed , and an actor-model like event messaging system.
This should mean even more squeezed performance while avoiding the cons of event-loops in high computation tasks, because you can easily switch to using a dedicated thread for those.
The internal messaging system can be used for decoupling services and easily separating them later if needed, and also provides implicit concurrency like the actor model.
Quarkus provides a layer over vert.x , making working with it easier and integrate it to the application under the hood.