API Best Practices: Hypermedia (Part 4.1)
This is part four, sub-series 1, of the API design best practices series. Read part one: Plan Your API »Read part two: Spec Driven Development »Read part three: Nouns,
API Best Practices: Nouns, CRUD, and More (Part 3)
This is part three of the API design best practices series. Read part one: Plan Your API »Read part two: Spec Driven Development » Once you have an
API Best Practices: Plan Your API (Part 1)
This is part one of the API design best practices series. Read the introduction to the series: New Series: API Best Practices » Understand WHY you
SOA School: Put your SOAP to REST
The benefits of applying the principles of SOA when catering to the IT needs of your organization are clear in a business-driven, vendor-neutral architecture.
Designing your RESTful API for Longevity
One of the greatest challenges API developers face is creating an API that is flexible enough to pass the tests of time and technology. In
Cross domain REST calls using CORS
To fight XSS attacks, the web browser imposes the same origin policy for HTTP requests made by JavaScript code: But there are a lot
Error handling in Mule 3.3: Catch Exception Strategy
We put a lot of effort in Mule 3.3 to improve error handling in Mule ESB. One of the most common requirements during error
GeoNames Cloud Connector for Mule
More and more companies are using geocoding at some point in their business processes. Geocoding can help companies take smarter decisions by offering customers
Introducing Mule Query Language
Working with web APIs, local APIs and different data formats and structures is too damn hard. You have to write painful verbose code to:
Securing REST Web Services against LDAP
Many Mule users create RESTful services but they are not always clear on the way to authenticate and apply authorization to a RESTful Web Service. I have seen