3 ms·
i recently wrote a small blog engine in vert.x (http://vertx.io/ http://vertx.io/). i'm not fluent with reactive programming yet (so i didn't use RxJava), but t
by stefs 11y ago
i recently wrote a small blog engine in vert.x (http://vertx.io/ http://vertx.io/). i'm not fluent with reactive programming yet (so i didn't use RxJava), but the callback hell was manageable enough. among the upsides are the seamless integration and handling of websockets. the blog engine is a bit of an outlier though because it's embedded and fully single threaded. there are a lot more advantages if you leave out the embedding, like several more languages (several languages with interpreters available on the JVM).
- k__ 11y agoI would recommend vert.x too. But only because I'm used to nodejs and this is the jvm equivalent.
- slantedview 11y agoVert.x is fantastic. My honest opinion is that JVM folks love complexity though. It's a mix of popularity, job security and good marketing that allow the traditional bloat-powerhouses to remain popular while technologies like Vert.x remain criminally under-utilized (see the rest of this thread for evidence). I don't know how or if this will ever change, but the downside for the JVM ecosystem overall is that people associate the JVM with things like Spring and Hibernate rather than things like Vert.x. And that's a shame.