George Reese, writing recently on his and Adrian Cole's experiences on using REST and SOAP APIs for developing Cloud applications, caused quite a stir in the community. What started as hints-and-tips has turned into a debate over whether there are real problems and misunderstandings around developing APIs with REST, irrespective of Cloud?
Some might prematurely conclude that REST has won based on Programmable Web data: 73% of the APIs are RESTful. But Steve Jones, a SOA practitioner, draws attention that those APIs are used by front-end systems doing data aggregation and not by the majority of enterprise systems, and REST is not yet ready for the enterprise.
The growth of Open APIs both in numbers and volume has surpassed any expectations over the last decade. John Musser from the ProgrammableWeb presented his analysis of the Open APIs State of the Market for 2011.
W3C has just released Candidate Recommendation SOAP over Java Message Service 1.0, defining how SOAP should bind to a messaging system that supports the Java Message Service (JMS).
The JAX-RS world now has at least 4 different implementations to choose from. But which is the best? Is that a valid question to ask at all? Well Solomon Duskis has set out to try to answer the question as best he can but comparing and contrasting the leading lights in this area.
The debate over REST vs. SOAP is really an age-old one. However it fired up again over a recent remark by XML guru Tim Bray that SOAP stack is an embarrassing failure.
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. In this article, Ganesh Prasad and Peter Svensson explains how and why.
In a blog entry, Spring Web Services lead developer Arjen Poutsma discusses the sad state of various SAAJ implementations in major application servers.
In this interview, recorded at QCon San Francisco, (then) Burton Group consultant Pete Lacey talks to Stefan Tilkov about the reasons for his disillusionment with SOAP, describes the ideas behind REST, and addresses some of its perceived shortcomings. Finally, he discusses cases where SOAP/WS-* or RESTful HTTP might be more appropriate.
When it comes to web services interoperability between .NET and Java, the choice used to be limited to SOAP over HTTP. Two new options recently became available in this area: WebSphere MQ (WMQ) and ActiveMQ transports can now be used for building interoperable web services between Java and .NET.
CXF is a fully featured Open Source Web Services Framework which people claim is easy to use and is industrial strength. CXF is also embeddable and people have used it often in combination with Spring. CXF is the combination of the Celtix and XFire communities coming together at Apache.
In one of the most entertaining presentations on the topic ever, Dr. Jim Webber debunks myths about the mainstream ESB concept and explains how a lightweight approach can yield real benefits without giving in to vendor pressure. Jim claims that an ESB often ends up being just a thin veneer on an existing mess, and how an approach that doesn't put intelligence into the network is superior.
A new article by Eran Chinthaka, Develop asynchronous Web services with Axis2, provides several examples of using the asynchronous APIs of Axis2 in client and server side applications.
KonaKart, a free Java-based online shopping cart, just released version 126.96.36.199. InfoQ spoke with KonaKart founder Paolo Sidoli to learn more about this release, and how KonaKart fits into the online shopping cart space.
Noemax releases a SOAP/TCP transport implementation for WCF, which makes use of the Fast Infoset in order to improve performance and interoperability of WCF services.