You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomee.apache.org by Milo Jaden <_m...@mail.com> on 2014/01/08 18:03:10 UTC
Vert.x Vs OpenEJB
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
Re: Vert.x Vs OpenEJB
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Side note: you are basically right but figures rarelly means anything
while not benched against YOUR env, saw it with vert.x as well so
putting it in the home page generally means you don't have anything in
your product (vert.x doesn't do it btw!)
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 Howard W. Smith, Jr. <sm...@gmail.com>:
> On Thu, Jan 9, 2014 at 10:19 AM, Milo Jaden <_m...@mail.com> wrote:
>
>> At the end of the day, I want to go back to my bosses and say, ‘OpenEJB is
>> simple, all we need is a single configuration file, openejb.json, and a
>> simple install of an OpenEJB.deb file on each of our nodes’. And bang we
>> have a high performant scalable Java EE server.
>
>
> Historically, posting your needs/concerns/issues/questions on this list,
> can and usually 'will' help you to meet your 'high performant scalable Java
> EE server' requirement.
>
> Also to reinforce that, there is now TomEE Tribe. you may want to reach out
> to them to get the added support that you are seeking.
Re: Vert.x Vs OpenEJB
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
On Thu, Jan 9, 2014 at 10:19 AM, Milo Jaden <_m...@mail.com> wrote:
> At the end of the day, I want to go back to my bosses and say, ‘OpenEJB is
> simple, all we need is a single configuration file, openejb.json, and a
> simple install of an OpenEJB.deb file on each of our nodes’. And bang we
> have a high performant scalable Java EE server.
Historically, posting your needs/concerns/issues/questions on this list,
can and usually 'will' help you to meet your 'high performant scalable Java
EE server' requirement.
Also to reinforce that, there is now TomEE Tribe. you may want to reach out
to them to get the added support that you are seeking.
Re: Vert.x Vs OpenEJB
Posted by Mark Struberg <st...@yahoo.de>.
regarding scaling: most of the standard Tomcat scaling solution applies to TomEE as well.
E.g. use a load balancer with sticky session in front of your servers. Then you can either use MSM (backup the sessions in one direction to a memcached instance) or tomcat session replication in pairs each. Means always 2 TomEE instances form a 'pair' which replicate the session to the other instance.
Those are the 2 standard approaches.
TomEE has a really good performance if you compare it with some 'big irons'. With a cluster of 8 servers you can easily serve a public internet app with 100k users.
There is a bit config needed, of course - but nothing too complicated.
LieGrue,
strub
On Thursday, 9 January 2014, 16:20, Milo Jaden <_m...@mail.com> wrote:
Hi,
>
>Thanks for everyone who responded, I appreciate all your comments :)
>
>There is no doubt that the support provided by the guys here is second to none, so hats off to them always.
>
>However, it is important to dive into facts and figures too.
>
>The two key problems that I have had with OpenEJB are configuration and scaling. This is likely due to there not being enough documentation on it. These two problems are very very important. I can’t emphasise this enough. In today's world, the ease of setting up a server side app and the performance and ease of scaling the app are mightily important.
>
>At the end of the day, I want to go back to my bosses and say, ‘OpenEJB is simple, all we need is a single configuration file, openejb.json, and a simple install of an OpenEJB.deb file on each of our nodes’. And bang we have a high performant scalable Java EE server.
>
>Additional benefits would be that when changing one openejb.json file on one of the nodes, it updates all the other nodes (with the same config file) it knows about. Likewise for a deploy command; you deploy an ejb-jar on one of the nodes and it instantly broadcasts it to all nodes. Is this possible with OpenEJB?
>
>Alternatively a nice admin tool to do this would be fantastic, again I’m asking, does this exist?
>
>Finally, if there were performance charts to show the number of requests OpenEJB can handle with varying number of nodes would be great! Additionally a guide on fine tuning the config file to set the correct number of threads for the various containers (Stateless, Stateful etc) to be optimised for the node hardware spec would be amazing!
>
>The thing with vert.x for example, is that they put scaling at the forefront.
>
>
>Thanks again to everyone,
>
>Milo
>
>
>On 9 Jan 2014, at 14:49, Howard W. Smith, Jr. <sm...@gmail.com> wrote:
>
>> On Wed, Jan 8, 2014 at 9:08 PM, LG Optimusv <lg...@gmail.com> 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.
>>>
>>
>> +1 agreed!
>>
>> also, kudos/thanks to David Blevins, Jean-Louis, John, and many TomEE users
>> as well for their posts/questions/etc... :)
>
>
>
Re: Vert.x Vs OpenEJB
Posted by Milo Jaden <_m...@mail.com>.
Hi,
Thanks for everyone who responded, I appreciate all your comments :)
There is no doubt that the support provided by the guys here is second to none, so hats off to them always.
However, it is important to dive into facts and figures too.
The two key problems that I have had with OpenEJB are configuration and scaling. This is likely due to there not being enough documentation on it. These two problems are very very important. I can’t emphasise this enough. In today's world, the ease of setting up a server side app and the performance and ease of scaling the app are mightily important.
At the end of the day, I want to go back to my bosses and say, ‘OpenEJB is simple, all we need is a single configuration file, openejb.json, and a simple install of an OpenEJB.deb file on each of our nodes’. And bang we have a high performant scalable Java EE server.
Additional benefits would be that when changing one openejb.json file on one of the nodes, it updates all the other nodes (with the same config file) it knows about. Likewise for a deploy command; you deploy an ejb-jar on one of the nodes and it instantly broadcasts it to all nodes. Is this possible with OpenEJB?
Alternatively a nice admin tool to do this would be fantastic, again I’m asking, does this exist?
Finally, if there were performance charts to show the number of requests OpenEJB can handle with varying number of nodes would be great! Additionally a guide on fine tuning the config file to set the correct number of threads for the various containers (Stateless, Stateful etc) to be optimised for the node hardware spec would be amazing!
The thing with vert.x for example, is that they put scaling at the forefront.
Thanks again to everyone,
Milo
On 9 Jan 2014, at 14:49, Howard W. Smith, Jr. <sm...@gmail.com> wrote:
> On Wed, Jan 8, 2014 at 9:08 PM, LG Optimusv <lg...@gmail.com> 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.
>>
>
> +1 agreed!
>
> also, kudos/thanks to David Blevins, Jean-Louis, John, and many TomEE users
> as well for their posts/questions/etc... :)
Re: Vert.x Vs OpenEJB
Posted by "Howard W. Smith, Jr." <sm...@gmail.com>.
On Wed, Jan 8, 2014 at 9:08 PM, LG Optimusv <lg...@gmail.com> 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.
>
+1 agreed!
also, kudos/thanks to David Blevins, Jean-Louis, John, and many TomEE users
as well for their posts/questions/etc... :)
Re: Vert.x Vs OpenEJB
Posted by Romain Manni-Bucau <rm...@gmail.com>.
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 <je...@gmail.com>:
> +1
> I would not have say better.
> Le 9 janv. 2014 13:26, "Mohammad Nour El-Din" <no...@gmail.com> 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 <_m...@mail.com> 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 <lg...@gmail.com> 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
>> >> <rm...@gmail.com>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 <rm...@gmail.com>:
>> >>>> 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 <_m...@mail.com>:
>> >>>>> 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
>>
Re: Vert.x Vs OpenEJB
Posted by Jean-Louis MONTEIRO <je...@gmail.com>.
+1
I would not have say better.
Le 9 janv. 2014 13:26, "Mohammad Nour El-Din" <no...@gmail.com> 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 <_m...@mail.com> 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 <lg...@gmail.com> 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
> >> <rm...@gmail.com>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 <rm...@gmail.com>:
> >>>> 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 <_m...@mail.com>:
> >>>>> 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
>
Re: Vert.x Vs OpenEJB
Posted by Mohammad Nour El-Din <no...@gmail.com>.
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 <_m...@mail.com> 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 <lg...@gmail.com> 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
>> <rm...@gmail.com>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 <rm...@gmail.com>:
>>>> 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 <_m...@mail.com>:
>>>>> 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
Re: Vert.x Vs OpenEJB
Posted by Milo Jaden <_m...@mail.com>.
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 <lg...@gmail.com> 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
> <rm...@gmail.com>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 <rm...@gmail.com>:
>>> 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 <_m...@mail.com>:
>>>> 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
>>
Re: Vert.x Vs OpenEJB
Posted by LG Optimusv <lg...@gmail.com>.
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
<rm...@gmail.com>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 <rm...@gmail.com>:
> > 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 <_m...@mail.com>:
> >> 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
>
Re: Vert.x Vs OpenEJB
Posted by Romain Manni-Bucau <rm...@gmail.com>.
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 <rm...@gmail.com>:
> 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 <_m...@mail.com>:
>> 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
Re: Vert.x Vs OpenEJB
Posted by Romain Manni-Bucau <rm...@gmail.com>.
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 <_m...@mail.com>:
> 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