Hybrid Messaging cloud allows your business to integrate your on-premise and site specific applications locally without the hop to the cloud using an on-site RoboMQ. Simultaneously, it connects SaaS and global enterprise applications using our middleware hosted on the cloud, creating a hybrid messaging infrastructure. Then the routing between local and cloud hosted RoboMQ happens seamlessly. Hybrid Messaging Cloud provides best of the both worlds with added architectural benefits such as fail-over to the cloud, redundancy, scale and nimble local messaging footprint. It is an ideal complement to your hybrid cloud architecture. It is well suited for businesses that need local integration in an environment where there is not always a reliable connection.
Our Hybrid Messaging Cloud allows your business to run applications on-site without constant and reliable connection to the cloud. Simultaneously, integration to SaaS and global enterprise applications can be run through our middleware on the cloud with built-in cache, buffering and retires, creating the perfect hybrid model.
Have you ever been in the middle of a business transaction and found that your local internet connection is not functioning as expected? With a traditional cloud set up your business could lose all the transactions made in that time, have to reenter them or even be forced to suspend activities until the problem is resolved. But with our hybrid cloud the transactions queued up until the connection to the cloud returns. The on-site or local applications continue to collaborate seamlessly using local link.
An alternative commonly used is to build cache mechanism in each of the on-site applications. This could be tedious and prohibitively costly. Why build cache in every application or be restricted to applications that have cache mechanism when you can use Hybrid Messaging Cloud?
Almost all medium to large businesses. Most businesses have centralized enterprise applications and localized site specific applications. This feature is very adaptable and can be personalized for the needs of your business. Hybrid Messaging Cloud offers a reliable integration mechanism for local applications to collaborate over local infrastructure without a long hop to the cloud. At the same time, local applications and enterprise applications can collaborate over federated link that provides resilience to intermittent network connectivity through local cache, buffering and built-in retries. Some examples could be retail establishments, resorts and hotel chains, restaurant chains and industrial establishments...
Hybrid Messaging Cloud provides fail-over, disaster recovery and ability to relocate applications smoothly in case of outages and issues. There are some additional security benefit of controlling what interactions happen locally vs. what goes through the public internet.
For more information on Hybrid Messaging Cloud and robomq's other products visit our website, robomq.io.
For us architects, being able to build modular, atomic, autonomous fine grained services which do just one job and do it well has been the panacea for all that was wrong with application development.
And to a large extent it is true. If we could build services that are atomic and fine grained, we should be able to minimize impact of change, increase code reusability, reduce test cycle times and be able to get products and services to market faster by assembling functionality instead of rebuilding it every time. Evolution in design, development and architecture practices have progressively tried to achieve this goal. SOA (Service Oriented Architecture) brought us closer to this goal than ever. The microservices architecture, which in some sense is a evolution of SOA (or a fix of all that went wrong with SOA) is now able to deliver the promise of building truly reusable and atomic services. It is the lego approach of building large complex and scalable business systems. Simple yet so efficient!!
And also, it is always about the right timing. Evolution of microservices coincides with greater adoption of cloud, virtualization and container technologies that provide the basic building blocks. The promise of microservices could not have been possible without the technologies like docker.
Most large scale web sites including Netflix, Amazon and eBay have evolved from a monolithic application architecture to a microservices architecture. amazon.com website application uses 100 to 150 microservices to get the data and assemble the web page. Netflix is doing the same for its applications. The very same model can be applied to almost all enterprise application development to increase reusability, develop code that is elastic to change, and to reduce cost.
We at robomq.io adopted this architecture early on. For all our integration services development, we have followed microservices architecture. The microservices architecture needs few simple building blocks :
Fortunately, we had all of it. We as part of RoboMQ product provide a multi-protocol gateway and the hosted message queue service. Multi-protocol gateway allows microservices to use variety of integration protocols without a constrain. It also allows easy integration with existing legacy services facilitating a brownfield approach. Message Queues as a service, including the hybrid messaging cloud, provides the wiring or the plumbing for services to interact, process and delegate tasks to each other thereby assembling complex business processes.
It has been a breeze developing services using microservices architecture and we are very happy about our choice. Now, we even do all our core product development using microservices architecture. We also started offering a microservices version of our platform for on-premise deployment. With this option you can simply run robomq on premise as docker containers and it takes the performance characteristics of the host machine.
In fact, we took a step further and identified that we could offer our platform as an enabler for Microservices and began offering it as one of the robomq.io product feature. Check out Microservices section under product.
There is also a ton of literature on microservices architecture on the web. I will encourage you to look at information from renowned architects like Chris Richardson and Martin Fowler. And of course feel free to send us a note at email@example.com to learn more.