Win a copy of Microservices Testing (Live Project) this week in the Spring forum!
  • 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
  • Tim Cooke
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Liutauras Vilda
  • Henry Wong
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Al Hobbs
  • Carey Brown
Bartenders:
  • Piet Souris
  • Mikalai Zaikin
  • Himai Minh

Jabber vs. JMS

 
Greenhorn
Posts: 23
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I'm working on a project where we're planning on using 'events' to notify different users REAL TIME of changes in entities they have expressed an interest in. Currently we have focussed on JMS to manage these 'events' but I've been looking into Jabber this weekend, thinking it might have possibilities.

Has anyone ever compared these two technologies - advantages vs. disadvantages? Anyone had experience in development using Jabber in an Enterprise application?
 
author and deputy
Posts: 3150
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Moving this question to
EJB and Other J2EE Technologies forum.
 
Ranch Hand
Posts: 98
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I don't know Jabber, but Jabber and JMS seem to offer different qualities of service, so it depends what you need. JMS will give you assured delivery (i.e. guaranteed "once and only once") with persistent delivery mode, or "at most once" with non-persistent (yeah, I know about DUPS_OK, but I don't want to complicate it!). It can even be transactional, although it doesn't sound like you need it. You can use durable subscribers to store messages for clients even when they are offline (or if they crash and restart).

As far as I can tell from the website Jabber seems to have no quality of service guarantee, so you're not sure if your message will arrive or not. The client will also need to be online to receive. These may or may not be a problem for you.

Apart from that there's the usual JMS 'advantages' - J2EE (easy to publish to an MDB, for example), standards, provider-independence etc...
 
Perry McKenzie
Greenhorn
Posts: 23
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks for the reply, Ben. Sorry I couldn't offer you more details as the the nature of the requirements, but I didn't know them myself.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic