an additional comment on jersey hibernate and so on add on in vertx: they are good etc but finally you are reimplementing a server which means you need to 1) understand how it works and how to make it working, 2) maintain it, 3) make it following versions. So once again depending the need it can be a good or very bad idea. JavaEE is just the rational way to do things but it means it is a bit late on some aspects that's why mixing both is generally a good idea keepin your app maintainable.
btw i'm not sure how you compare vertx to openejb, vertx/tomee could but vertx/openejb is like http/oracle (caricaturing but here is the idea). Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014/1/9 Jean-Louis MONTEIRO <[email protected]>: > +1 > I would not have say better. > Le 9 janv. 2014 13:26, "Mohammad Nour El-Din" <[email protected]> a > écrit : > >> Hi Milo >> >> I will just repeat what Romain said but in a different way, the >> Software Development world now is more broad and facing more >> challenging problems than a decade ago for example with a lot of >> technologies emerging that made using the web (and computer powered >> devices and gadgets) and the enormous amount of content and data users >> are producing and consuming these days, so that required finding more >> tools to handle that >> >> This does not mean by anyway that technologies like JEE can not handle >> such loads, maybe might not be the best or better than other >> technologies specifically developed for that purpose, but on the other >> hand they are not as tested and well proven in the field when it comes >> to enterprise (business) applications like JEE for example (among >> other technologies) >> >> I would say in the last decade we had fewer tools than we have now, >> but that does not mean that newer technologies totally replace current >> ones on the contrary, I believe that a good Software Developer should >> be aware about all the options available and how to use any of them >> either separately or in combination >> >> Actually I would be interested if you have experience using these >> technologies in combination and give us some insights about that >> >> On Thu, Jan 9, 2014 at 1:25 PM, Milo Jaden <[email protected]> wrote: >> > Well vert.x has quite a few mods. I’ve heard of people use hibernate for >> JPA. Also there are mods for rest such as jersey. >> > >> > On the scenario where all you need is a callable API (via REST or >> WebSockets) plus data handling such as JPA or MongoDB etc, then it looks >> like Vert.x seems very good. >> > >> > The other benefit is the fact of configuration. In simple language, >> OpenEJB is not simple to configure. >> > >> > Also I’ve struggled to find documentation on scaling OpenEJB, there are >> a couple of pages on Multipoint etc but no real guide on how I would scale >> OpenEJB. For example Glassfish has tools to manage multiple instances etc. >> Is there anything like this for OpenEJB? >> > >> > I would very much like to see a performance chart for scaling OpenEJB. >> Also, how to optimise the number of threads for the OpenEJB daemons etc. >> > >> > Personally using any server side platform for front end is something I >> don’t believe in anymore. I think any front end app should be programmed in >> client side code purely (so JavaScript, AngularJS, Ember, Dart etc). It >> makes things much more portable (especially when you think of mobile). >> > >> > >> > On 9 Jan 2014, at 02:08, LG Optimusv <[email protected]> wrote: >> > >> >> Romain, with all of your wonderful answers about everything (not just >> >> TomEE), you are the person that makes me (and maybe other people) to use >> >> TomEE. Thank you very much. >> >> >> >> >> >> On Wed, Jan 8, 2014 at 12:07 PM, Romain Manni-Bucau >> >> <[email protected]>wrote: >> >> >> >>> 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 >> >>> >> > >> >> >> >> -- >> Thanks >> - Mohammad Nour >> ---- >> "Life is like riding a bicycle. To keep your balance you must keep moving" >> - Albert Einstein >>
