Win a copy of Five Lines of Code this week in the OO, Patterns, UML and Refactoring 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 all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
Bartenders:
  • Piet Souris
  • Frits Walraven
  • Carey Brown

Synchronus JMS Vs. HTTP request-response for SOA

 
Ranch Hand
Posts: 89
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I don't know if this question fits under Other Java EE Technologies but here is my question,

For SOA architecture what is better synchronus messaging through JMS or a simple HTTP request/response scenario?

What are the advantages of choosing either of the two?

Thanks,
 
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I assume with req/resp over http you meant RESTful web services. If you can make a choice, go for simple RESTful XML over http solution. Coz, you dont need any additional middleware infrastructure and in synchronous messaging your communicating systems are tightly coupled. More loosely coupled solution is a better SOA.

In case you meant otherwise, it is good to opt for a SOAP based web service or a RESTful web service based on your specific needs.
 
K Aditi
Ranch Hand
Posts: 89
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
But what about JMS?Is it a viable option?
 
author
Posts: 580
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Aditi,

JMS is a viable option for service producers and consumers that can do messaging such as Java applications, Microsoft systems using MSMQ and mainframe applications that use MQ-Series. In practice, this works inside the enterprise and between close B2B partners. For generally consumable services,
SOAP or REST is better.

Cheers,
Reza
 
K Aditi
Ranch Hand
Posts: 89
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Kumar and Reza thanks for the response.
 
Reza Rahman
author
Posts: 580
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
My pleasure.

Cheers,
Reza
 
You've gotta fight it! Don't give in! Read this tiny ad:
Thread Boost feature
https://coderanch.com/t/674455/Thread-Boost-feature
    Bookmark Topic Watch Topic
  • New Topic