3 ms·
I know of a few large production systems that have dispensed with typical servlet containers completely and are based on Netty's HTTP codecs instead, but as you
by bborud 14y ago
I know of a few large production systems that have dispensed with typical servlet containers completely and are based on Netty's HTTP codecs instead, but as you said, the people who do these systems aren't necessarily bloggers.
I think this is a very positive trend towards more minimal software and more self-contained Java servers. Being able to ship (server) software as a single JAR file with everything you need embedded makes life a lot easier. It is very nice not having to fiddle around setting up servlet containers, configuring them, deploying applications into them and then, inevitably, having to restart everything when a rogue application decides to ruin the party for everyone. (And it just gets worse when you try to automate it).
One thing I'm still looking for is a good skeletal project for a REST server making use of JAX-RS annotations, Netty and having support for asynchronous request handling. Something that we could turn into a really skinny Maven archetype and teach new programmers to use.
(Obligatory disclosure and shameless plug: I work for Comoyo. If you find these things interesting/exciting and would like to come work for us feel free to contact us. We're hiring :) )
- swah 14y agoDropwizard has some examples of "REST server making use of JAX-RS annotations", but then its not Netty, but Jetty.
- bborud 14y ago(I see cgbystrom commented further up and kinda hoped he would whip up a JAX-RS+Netty+async request processing skeleton ;-) )
- cgbystrom 14y agoTotally agree about having smaller and more contained apps. I used https://github.com/cgbystrom/jersey-netty https://github.com/cgbystrom/jersey-netty for a one-off project wiring Jersey together with Netty. But it's not async :)