Marc de Graauw challenges the notion that transport-level reliability mechanisms like WS-ReliableMessaging are needed, showing how business-specific logic for in-order and exactly-once processing do the job much better with examples from Dutch Healthcare's SOA.
Web developers today have a myriad of technologies they can choose from; for example, the two approaches for interfacing to the web with web services, namely SOAP and REST. Both approaches work, both have advantages and disadvantages to interfacing to web services, but it is up to the web developer to make the decision of which approach may be best for each particular case.
William El Kaim, Lead Architect at Carlson Wagonlit, provides a rare glimpse at all the choices, and the rationale behind them, he and his colleagues have made while building their organization's Service Oriented Architecture. How does your SOA compare? What will be the major evolutions in the next few years? How will the Cloud impact current SOAs?
Brian Sletten discusses REST architecture, SOAP and WS-*, Semantic Web, URLs as IDs, URIs and URNs, freedom of form, logically-connected late-binding systems, HATEOAS, and the impact of Semantic Web. 19
SOA is 10 years old. InfoQ has gathered Jeff Andres, Eric Ballou, Dave Hollander and William El Kaim, all experienced Enterprise Architects, to share their perspectives as part of a virtual panel. 3
Java Message Service 2nd Edition by Mark Richards covers JMS topics like Publish-and-Subscribe & Point-to-Point, Messaging Filtering and Transactions. InfoQ spoke with Mark about his new book.
Joern Barthel introduces the Advanced Message Queuing Protocol (AMQP), and illustrates it's useage from a Ruby app with the open source RabbitMQ server on the backend (which is written in Erlang). 1
Message routing is an essential consideration for middleware. This article addressed the use of Mule middleware to implement flexible message routing services. 2
Thin client paradigm characterized by web applications is a kludge that needs to be repudiated. Old compromises are no longer needed and it's time to move the presentation tier to where it belongs. 24
Udi Dahan's team averts a second failure using service contracts to address multiple dimensions of scalability. 2
InfoQ is pleased to provide a hosted chapter from the recently published "Essential Windows Communication Foundation" authored by Steve Resnick, Richard Crane, and Chris Bowen.
InfoQ spoke to the lead developers of the most important open source Java Web-services stacks about their design goals, standards, data binding, XML, interoperability, REST support, and maturity. 12