-
1. Re: HornetQ vs MRG
clebert.suconic May 24, 2011 10:24 AM (in response to talawahdotnet)In product terms:
- HornetQ is for EAP
However the community version will still have a standalone distribution
- MRG is for standalone
AFAIK there's a JMS client through qpid-java. I'm not sure if it's 100% compatible with XA implementations... etc.
These are more marketing questions and I'm not qualified to answer them properly. You should probably address these questions through marketing.
-
2. Re: HornetQ vs MRG
timfox Jun 5, 2011 6:06 AM (in response to clebert.suconic)I should add a few more things (I'm sure Clebert would like to say them too, but he works for Red Hat so has to tread more carefully )
1) HornetQ has far superior performance to MRG
2) HornetQ has a broader feature set than MRG
3) HornetQ is productised as part of EAP but it's a fully standalone messaging system too. If you want to run HornetQ standalone and fully supported, then buy an EAP subscription and just turn off those services in EAP you don't want (e.g. EJB etc) - it's just configuration.
-
3. Re: HornetQ vs MRG
talawahdotnet Jun 18, 2011 5:58 PM (in response to timfox)Thanks for the additional insights Tim. Good to see you are still somewhat involved even though you are sleeping with the enemy now
I guess even companies like Red Hat have cases where politics gets in the way of good technology. It is really hard to fathom that the RH product/marketing guys don't realize that AS7, Infinispan and HornetQ make a compelling combo. If they feel that AMQP is the future, then the should be adding it to the HornetQ roadmap rather than WONTFIXing it, and promoting MRG-M in its place.
-
4. Re: HornetQ vs MRG
yairogen Nov 18, 2012 8:17 AM (in response to timfox)I'm looking into using HornetQ in production using an ERAP license. Can you pleae send me some info on EAP 6 - how to disable everything but HonretQ?
Thanks.
-
5. Re: HornetQ vs MRG
jbertram Nov 18, 2012 7:37 PM (in response to yairogen)If you need help with something related to EAP then you should open a ticket on the Red Hat Customer Portal. Using community support when you have an EAP subscription is not optimal.
-
6. Re: HornetQ vs MRG
clebert.suconic Nov 27, 2012 7:14 PM (in response to yairogen)I have taken standalone-full.xml on jboss 7.1 and removed everything except to what is needed (JNDI, remoting for JNDI remote, admin, security), and it worked.. it would be the equivalent for our standalone. (It's actually a better deal since you get the CLI from JBoss 7).
I will attach the config I've made here:
-
standalone-messaging.xml 11.0 KB
-
-
7. Re: HornetQ vs MRG
dpocock Mar 6, 2013 4:56 AM (in response to talawahdotnet)I've created an issue in JIRA asking for clarification about this situation:
-
8. Re: HornetQ vs MRG
clebert.suconic Mar 6, 2013 8:27 AM (in response to dpocock)JIRAs are for Bugs.. and usually after a discussion on the user's forum... not a place for political clarifications and discussions. I've rejected it.
-
9. Re: HornetQ vs MRG
dpocock Mar 6, 2013 8:45 AM (in response to clebert.suconic)Why is there something `political' about asking for missing information about the relationship between the MRG and HornetQ roadmaps?
As I noted in the Jira, Redhat has already provided slides explaining the roles of MRG and Fuse MQ in the roadmap:
http://www.redhat.com/promo/jboss_integration_week_sessions/pdf/MessagingRoadmap_10-16-12.pdf
and the HornetQ logo is on slide #18, but there is no other reference to it, I don't want to speculate what this means, rather, I am just hoping to see a more thorough statement about the strategy and relationship between the products.
-
10. Re: HornetQ vs MRG
jbertram Mar 6, 2013 2:00 PM (in response to dpocock)You're asking about Red Hat commercial products on a community project forum - which is the wrong place to ask. If you want to know more about Red Hat commercial you should contact your Red Hat sales/account representative (assuming you have one).
-
11. Re: HornetQ vs MRG
clebert.suconic Mar 6, 2013 10:37 PM (in response to dpocock)Forget the political part.. I didn't mean on that... what I meant was JIRA is not a place to request information (not our JIRA at least) about product relations... etc
.. It's a place for feature requests and bug features.. and even then we usually request users to go through the forums first.