#### Building the event mesh with Camel This blog is part one of my three blogs on how to build a hybrid multi cloud event mesh with Camel. In this part I am going over what inspired me to do the demo, and architecturally how everything is put...
This blog is part one of my three blogs on how to build a hybrid multi cloud event mesh with Camel. In this part I am going over what inspired me to do the demo, and architecturally how everything is put together. I will be using Red Hat OpenShift (Kubernetes) as the platform for my mesh. And using Kafka as the backbone to stream/persist events and last but not least using Apache Camel (in Red Hat Integration) to weave the mesh across Service Now, Amazon AWS, Microsoft Azure and Google Cloud Platform.
The whole reason why I'm doing this is because I'm seeing trends from our customers. More than 50% of the CTO and architect we interview are moving at least part of the workload to either a single cloud or multiple clouds. And not surprisingly most would also have in-house data centers and purchase SaaS services. And it got me thinking, what are the possible ways to bridge and connect everything? What are the challenges we will face when trying to connect the dots?
Taking a look specifically from the integration side. As more applications, services and functionality are deployed across geo, data centers and clouds, you will start to see problems arise:
Service Silo: Possibly causes could be geo regulation, how the company structure the teams, deployment policies or vendor specific features. Services were NOT effectively reused, simply because it’s hard to get to. Or not even know among different teams.
Data Integrity: Keeping the data in sync across the multi-cloud can be challenging. Event driven architecture can help by streamlining real-time events simultaneously across multiple clouds, events can be changed from state, request or command. To achieve eventual consistency, and the faster the broader the events gets to, the more real time it can achieve.
Integration Mess. Having many point to point could lead to disarray of connections. And it will definitely affect how fast to deliver change for your application. As there are no organized and holistic view of where the events are going and the subscriber of the events.
Mismanagement of multi-cloud expense costs an arm and leg to business and its management has become a major pain point. Here we break down some crucial tips to take some of the management challenges off your plate and help you optimize your cloud spend.
To move or not to move? Benefits are multifold when you are migrating to the cloud. Get the correct information to make your decision, with our cloud engineering expertise.
Why Is a Hybrid Cloud Approach the Best for Cloud? Learn the five reasons why a hybrid cloud approach is the best approach to cloud and how the hybrid cloud benefits the security of your information.
IBM has announced new and enhanced services to help organisations manage their cloud security strategy. These services integrate cloud-native, IBM, and third-party technologies to create a unified security approach across cloud ecosystems. Learn IBM’s New Hybrid Cloud Security Services.
App Modernization + Hybrid Cloud Architectures With Apache Kafka [Video] Apache Kafka is a battle-tested technology for hybrid cloud architectures to integrate legacy infrastructure and cloud-native microservices. Video and Live Demo of Hybrid Replication With Kafka.