Advanced API Patterns with RAML

advanced raml design

The vast majority of RESTful APIs follow a simple “request-response” message exchange pattern, but that pattern is often too limiting and is not sufficient to achieving robust and reliable application performance.  We frequently get questions from customers asking:  ‘How I design asynchronous APIs?’ and ‘How I design an API that allows for the concurrent modification of the same API resource without bringing the resource into inconsistent state?’.  In this blog post, we present two approaches answering these questions using standard HTTP headers and status codes.

Cheat Sheet: Asynchronous Message Processing

January 31 2013

1 comment.
motif

You want to get more done in 2013 so you’re going to need to switch from synchronous to asynchronous processing to do more with the same resources.  Mule started life as an asynchronous message engine and has a lot of capabilities and optimisations built in for processing data concurrently. To help you understand asynchronous processing in Mule we have created this cheat sheet that will help you understand the basics.