When we started building a new Web API for our business we wanted to build a really great API and the answer on Internet was to build a RESTful API, Amy Palamountain revealed in a recent presentation at TechEd in New Zealand when sharing her experiences of how to build a RESTful API based on the core ideas of HTTP and the web.
"Don't version unless you absolutely must, and it is rare that you absolutely must" says Mike Amundsen in a series of API design workshops he held recently. Amundsen describes the "USE" paradigm for API design focussing on usability, scalability and evolvability. He describes the three most common styles of API implementation and how they compare to these principles.
In late December 2011, Microsoft announced the pre-release of a set of services labeled Windows Azure Service Bus EAI Labs. These enhancements to the existing Windows Azure Service Bus make it easier to connect (cloud) applications through the use of message routing rules, protocol bridging, message transformation services and connectivity to on-premises line of business systems.
A recent paper published by researchers in Germany reveals multiple security vulnerabilities in Amazon Web Services (AWS) and Eucalyptus's SOAP and web interfaces. The flaws are related to architectural choices which impacts multiple users and the overall cloud security.
SmartBear Software, a prominent ALM and monitoring tool vendor acquired Eviware, creators of popular open source web services testing tools soapui and loadui, last week.
SOA Software entered the API management portal market with their release of the Atmosphere portal. The Atmosphere platform ensures security, robustness and availability of enterprise APIs over the right range of interface types. In this article we delve into the reason behind the evolution from enterprise SOA and cloud governance to API management and other technical details around the offering.
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.