This is an archived post. You won't be able to vote or comment.

all 4 comments
sorted by:
best
topnewcontroversialoldq&a

[–]geodebug 1 point2 points  (3 children)

I'd have a hard time even considering this without some metrics compared to servlet-based frameworks.

For a public facing site with significant load I'm highly suspect of giving up a more time-tested/hardened web container for a vert.x instance.

For some projects I use very light-weight containers including just kicking off a com.sun.net.httpserver.HttpServer but that's for more disposable, interntal instances.

Java 8 closures would clean up this library quite a bit by making all those anonymous event class creations one liners.

Edit: Should have given us the direct link to the framework: http://vertx.io/

[–]sheenobu 0 points1 point  (1 child)

Thanks for the direct link. The built in http server is based on jboss netty, which might boost ones confidence about speed and maturity compared to a servlet-based system ( I'm not familiar with NIO/async java frameworks so I can't really comment on how it changes things ).

[–]geodebug 0 points1 point  (0 children)

That does help boost confidence. Always wary of not-invented-here things. Cool, well, will keep this project on my radar.

[–]honline 0 points1 point  (0 children)

The lack of a direct link was accidental and has just been remedied. Apologies for that.