It used to be pretty easy to pick the technology you’d use to connect applications to information sources, services and people.
But increasingly, most applications look like “all of the above.” A corporate mobile app might need information from several back-end data sources to support a field sales team. And an Internet of Things application may push data over the wireless internet to cloud-based storage and an internal big data store so it can be analyzed by a CEP engine. Which is the best choice then – a messaging architecture, or a REST-based web architecture? And if the answer is “both, ” how will you bridge the two environments to pass state and semantics?
Wouldn’t it be great if you could have both environments work together seamlessly, getting the best of both worlds? That’s what we’ve enabled with the new 7.1 release of SolOS, the software and firmware that makes up the Solace platform. By supporting REST over HTTP within our message broker and letting you map REST posts to the features of a message bus, we give architects and developers their cake and enough forks to enjoy a sustained sugar high.
The value of such a platform depends on where you’re coming from:
Thanks to this release something that has always been a key decision – messaging or HTTP – is now an unnecessary choice. Each architectures is good at solving a different kind of problem, and together they can each take care of what it does best while giving developers the flexibility to build the next generation of high volume and high value applications.