PS: if you don't need JPA, JTA (transactions), JAXRS, container (injections, resource, ...) etc you can have a look to vertx.. Another point is to think to maintainance and knowledge of your teams. That's why mixing both can be interesting even if imposing some limitations: you get the most of both. Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau
2014/1/8 Romain Manni-Bucau <[email protected]>: > well I already used both together, openejb for the backend and vert.x > for the front...but honestly it depends a lot on your app and there is > no magic answer to such a question > Romain Manni-Bucau > Twitter: @rmannibucau > Blog: http://rmannibucau.wordpress.com/ > LinkedIn: http://fr.linkedin.com/in/rmannibucau > Github: https://github.com/rmannibucau > > > > 2014/1/8 Milo Jaden <[email protected]>: >> Hi, >> >> I wanted to spark a little debate on what people thought about vert.x, a >> scalable jvm platform. Its built on top of netty and provides the ability to >> write modules (they call verticals) in several different languages. >> >> They also have some impressive performance charts: >> http://www.cubrid.org/blog/dev-platform/inside-vertx-comparison-with-nodejs/ >> >> I especially would like to hear from the TomEE contributors as to why they >> would advise sticking with TomEE/OpenEJB rather than something like vert.x >> (especially for the scenario where all you do is REST + data calls and don’t >> need JSP etc). >> >> Regards, >> >> Milo
