• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Tim Cooke
  • Jeanne Boyarsky
  • Liutauras Vilda
Sheriffs:
  • Frank Carver
  • Henry Wong
  • Ron McLeod
Saloon Keepers:
  • Tim Moores
  • Frits Walraven
  • Tim Holloway
  • Stephan van Hulst
  • Carey Brown
Bartenders:
  • Al Hobbs
  • Piet Souris
  • Himai Minh

Message Producer Consumers

 
Ranch Hand
Posts: 441
2
Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Suppose we have a message producer application which is utilizing ActiveMQ to produce the messages. Is it possible to have a consumer written using any other implementation such as IBM MQ or HornetQ etc?

Will it be able to parse and process the messages across different messaging APIs?
 
Saloon Keeper
Posts: 7411
170
  • Likes 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
These products all support JMS, don't they? So there should be no interoperability issues as long as you use only JMS to interact with them.
 
Vaibhav Gargs
Ranch Hand
Posts: 441
2
Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thank you Tim for your response.

We have some implementation specific features provided by different vendors. So, if someone uses those features, then, i believe producer and consumer must be implemented using same implementation. So, is it a good approach to couple the implementation product.
 
Tim Moores
Saloon Keeper
Posts: 7411
170
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

is it a good approach to couple the implementation product.


If you are using several different messaging servers that need to interoperate, then no - using implementation-specific features doesn't sound like a good idea. OTOH, these features might be orthogonal to JMS, so if one client uses them, other clients might still be fine using JMS. Depends on what those features are, obviously.

Are you trying to consolidate messaging servers? That's what I would prefer to do if I were faced with multiple servers. Of course, JMS exists precisely so that a client can connect to different servers using the same API, so this may not be a pain point for your organization.
 
Vaibhav Gargs
Ranch Hand
Posts: 441
2
Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Some of the applications are using ActiveMQ and some are using HornetQ. And, we are planning to integrate them all. So, what would be the best integration strategy?

I was just wondering if they were using some implementation specific features in messages, then, how it will be handled across multiple vendors?
 
Tim Moores
Saloon Keeper
Posts: 7411
170
  • Likes 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
As I said, that depends on what those features are. They may or may not be relevant to JMS. Hopefully, the documentation of those servers talks about how JMS works (and interoperates) with vendor-specific features.

we are planning to integrate them all.


I was asking about consolidating them. Integrating them would involve using an API like JMS that works with all implementations.
 
You're not going crazy. You're going sane in a crazy word. Find comfort in this tiny ad:
the value of filler advertising in 2021
https://coderanch.com/t/730886/filler-advertising
reply
    Bookmark Topic Watch Topic
  • New Topic