With four years under our belts, we recently decided to look back at why we started RoboMQ, and we wanted to share that story with you!
Four years ago around 2012, our founder & CEO Bramh Gupta was running middleware for telecom companies, managing critical business processes necessary for telecommunication business operations. This included activities like cellular device activation & provisioning, where more than twenty to twenty-five systems will interact in less than 3 minutes to light up a cellular device on the network and create all the needed artifacts across telecom systems to onboard new customer. This was an operation of a massive scale when you think about tens of million of customers for a telecom operator.
With adoption of Cloud, SaaS applications and emergence of IoT back then, it was clear to our founding team that the existing integration platforms and the middleware technologies were not fit the coming world. No SaaS or cloud application provider will code to or provide interfaces in proprietary APIs of likes of TIBCO or IBM.
“What the world really needed was a middleware that has no proprietary APIs or is API less, but can integrate with any of the hundreds of standard device and application protocols or APIs with conversion taken care at the core in the middleware itself.”
RoboMQ was born with this idea. Fred Yatzeck who had a long stint in integration middleware working along Bramh in telecom days formally joined the founding team to start shaping this dream to reality.
RoboMQ adopted containerization technologies and Microservices early on. We provide microservices based integration framework including visual business process designer for microservices. This passion went so far as to running the core platform itself as docker containers.
Another problem with the existing middleware technologies is the hub and spoke architecture that often fails at the center. RoboMQ solved this problem by creating a federated and distributed messaging fabric or a mesh, “Hybrid Messaging Cloud”, that can run on the cloud, on premise, or even on IoT gateways and single board computers (SBCs).
The result is a highly decoupled and distributed integration platform that treats devices, IoT gateways, SaaS applications and enterprise systems all as “first class citizens”. This allows you to build business workflows across clouds and networks to save cost or create new revenue generation opportunities.