4 ms·
I recently discovered Dropwizard, which I found to be incredibly easy to use and eminently readable. The example code I saw for Vert.x, on the other hand, remin
by Cyranix 14y ago
I recently discovered Dropwizard, which I found to be incredibly easy to use and eminently readable. The example code I saw for Vert.x, on the other hand, reminded me of the "callback spaghetti" I've heard lamented as a problem in NodeJS. Do I have a poor first impression? Can someone sell me on Vert.x for web-facing applications? Am I the wrong audience because I'm using other technologies like RabbitMQ to handle distributed polyglot work? [Apologies if I come across like a hater, because I'm not; I'm genuinely confused about whether Vert.x represents an improvement or an alternative to my situation.]
- spartango 14y agoWe're using Vert.x internally to do basically all of our IO (network client and server, disk) in an asynchronous manner, because its API is super simple and elegant. Because much of our other code is already asynchronous and event-driven, Vert.x fits in nicely. The callback hell is certainly something that you can run into , but we've created a sane Java construct to avoid it: https://gist.github.com/727425ac3069f6465959 https://gist.github.com/727425ac3069f6465959 The neat part of this construct is that it decouples the API from the implementation. I haven't quite tried to sell you on Vert.x here, but feel free to reach out to me if you have questions. We're really liking Vert.x so far.