If you’re an enterprise developer of mobile or web applications, you’ve probably used HTTP and a RESTful API to post data into your app server which in turn connected to a message bus for distribution to back-end assets. Getting data flowing back and forth is the tip of the iceberg – the real work lies in making it performant and resilient, and of course testing the heck out of it. That’s where direct easy access to a message bus can seriously accelerate your coding by taking care of those tedious parts of building, testing and deploying bulletproof services.
Here are some examples of what you get when a fully featured message bus is available to your application development:
Web application design has revolutionized rapid prototyping and accelerated the delivery of services, and REST/HTTP have proven to be a flexible way to connect clients and servers across such an architecture. Bringing the power of a message bus to these applications makes it faster to develop advanced functionality, integrate from client to rich back end services and simplifying operations.
You may also want to check out this post Adding REST to Your Messaging to understand what those used to traditional messaging middleware get out of REST/HTTP from their perspective, and this overview of what it means to offer REST support in a messaging middleware platform.