Over the past few years many people – I amongst them – have spent countless hours convincing you that RESTful interfaces can (and have) changed the face of application integration. But it’s 2016, and as ever, market forces now dictate that REST and HTTP aren’t suitable or effective in every integration scenario.
In previous blogs we’ve highlighted some limitations, and potential pitfalls of REST. In this blog I want to discuss a way to overcome these limitations using realtime messaging – and in particular Diffusion Cloud.
Regular readers will know the Diffusion SDKs make it really easy to integrate realtime messaging with backend systems. Importantly, changes to the backend are rarely required so any legacy interface – or indeed RESTful interface – can easily be turned into a streaming realtime API.
Across many REST interfaces, it’s common to see clients poll continuously as they check for changes in data they are interested in. This creates significant load on the API Gateway layer, or the backend service directly and often means the integration tier has been sized to support entirely redundant traffic – which is unnecessarily costly. By using realtime messaging from Push Technology, we can massively reduce the need for polling.
By creating a publisher in Diffusion Cloud that connects to a RESTful API, only a single connection to the backend API is required. The Push server will periodically poll the backend, but will only send data to the client applications when a relevant change it detected.