InfoQ

News

InfoQ Article: Secure and Reliable Web Services

Posted by Miko Matsumura on Jul 04, 2006 08:55 AM

Community
SOA
Topics
Web Services ,
WS Standards
Tags
WS Basic Security Profile ,
WS-ReliableMessaging
Organizations have numerous IT systems that need to exchange structured data, both within (A2A, EAI) and between organizations (B2B). The exchange of these data is handled in many different ways. The different solutions lead to incompatibility, delays and extra costs when setting up new links between systems or re-using existing ones. Web Services can become the single standard for all exchange of structured data. After waiting over 5 years, 2 important Web Services specifications have finally been endorsed: WS-Security and WS-ReliableMessaging. Will these specifications allow the adoption of web services as a standard for all communication within and between organizations?

Guy Crets, partner at Integration consultancy Apogado has written an article for InfoQ addressing these questions. Read Secure and Reliable Web Services.

Guy concludes:
When secure, reliable and standard Web Services come true, the same technology can be used for synchronous and asynchronous communication both within and between organizations. First of all, this can lead to a very important cost reduction and commoditization. Secondly, Web Services technology becomes an important enabler for Service Oriented Architecture. Services can easily and quickly be published and consumed within and between organizations, leading to an enormous flexibility.

2 comments

Reply

Good writeup, but feels like a letdown! by Michael Burke Posted Jul 5, 2006 12:16 AM
Re: Good writeup, but feels like a letdown! by Guy Crets Posted Jul 5, 2006 9:43 AM
  1. Back to top

    Good writeup, but feels like a letdown!

    Jul 5, 2006 12:16 AM by Michael Burke

    I thought this was a neat little summary, which is firmly rooted in the real, messy world as opposed to the imaginary picture often painted by vendors, book authors and consultants.

    I was kind of hoping that an attempt would be made to answer the hypothetical questions raised in the summary and throughout the article.. what does the author actually *think* will happen? I get the feeling there's skepticism - why?

    Are there other competing standards in the offing (seems to be par for the course in the WS-* world)? Are there complications that may hamper adaption?

    I get the feeling a lot of people are waiting to see how this plays out before betting on a horse. The fact that WS-ReliableMessaging is based on a non-ratified standard (WS-Addressing) shows that this stuff is still in its infancy.

    I don't think most people will be making a choice anyway - it will simply turn out that large players (eg Walmart!) choose a platform, and everyone scurries to integrate. Let's just hope that a vast majority of large players make the same (and 'right') choice.

  2. Back to top

    Re: Good writeup, but feels like a letdown!

    Jul 5, 2006 9:43 AM by Guy Crets

    Michael,

    I must confess that I was pretty disappointed when I learned some time ago that Microsoft WCF (aka. Indigo) would not support persistent WS-RM messaging. But I keep hoping: nice, persistent WS-RM implementations from e.g. BEA or CapeClear are very promising.

    I remain convinced that Web Services are the way to go. A single, secure and reliable XML based protocol will really do wonders.

    Therefore, I'm not that enthousiastic about the new AMQP protocol. This protocol can be used within the corporate firewall. But WS-RM (or WS-RX) holds the fantastic promise of one single protocol both within and between organizations.

    My recommendation: "contract first", start focusing on the message formats, make a language out of the XML alphabet soup. Get the upper layers of your systems to talk XML!

Exclusive Content

Diary of a Fence Sitting SOA Geek

In this presentation, Mark Little explains the history of SOAP/WSDL/WS-*-based web services and RESTful HTTP and highlights how the two approaches might converge into a single solution.

Flex for XML and JSON

Platforms need interoperability. In this article Flex interoperability with JSON and XML is explored including direct mapping to chart and grid components.

Measuring Agile in the Enterprise: 5 Success Factors for Large-Scale Agile Adoption

Michael Mah analyzes the development process in 5 companies: 2 Agile (one of them BMC) and 3 classic. He presents the factors which contributed to the success of BMC's Agile adoption.

Tom Preston-Werner on Powerset, GitHub, Ruby and Erlang

In this interview filmed at RubyFringe 2008, Tom Preston-Werner talks about how both Powerset and GitHub use Ruby and Erlang, as well as tools like Fuzed, god, and more.

David Laribee on Alt.NET and its Mission

David Laribee discusses the purpose of ALT.NET, its mission and future.

Discover RailsKits and Stop Writing Redundant Code

Ruby on Rails has become a popular Ruby framework for creating web applications in recent years. An aspect of creating a web application is the need to repeatedly create the same base functionality.

A Formal Performance Tuning Methodology: Wait-Based Tuning

Steven Haines talks about tackling web application performance tuning by proposing a method called wait-based tuning.

Shaw and Fowler About Forging a New Alliance

Shaw and Fowler talk about the need for a new relationship between the business department and the IT department. Studies have shown that projects mostly fail due to miscommunication between the two.