The concept called event mesh, especially for large distributed systems would become a mechanism to move your data in a smooth manner. Interactions would be more asynchronous, says Sumeet Puri, SVP & Global Head of Field Technology, Solace Corporation.
Businesses are transforming. India is leading the payments gamut in a huge way and Solace is a part of it to some extent. Payments, just a few years ago, dealt with very large volume and low volume. Architectures were service oriented and very siloed. This is changing rapidly especially with the advent of mobility, said Puri.
“So, the revolution India has seen in affordable data on phones and smartphones is unbelievable, nothing like that in the world where a million customers were added for six months in a row by reliance Jio and as a result of that other telecom stepped up their game and the penetration has been massive,” he said.
“Which means that more and more e-payments have started and the next generation is anyway branch lazy and digital friendly with that if you look at the architectures in a bank for that matter any enterprise it tends to be a huge monolith. It’s like a huge mothball and if you pull one string it disturbs the entire ecosystem.”
So how do you keep yourself ready against these digital disruptive skills when you have an old architecture to some extent?
Puri explained,” In the past ten years, this is how technology from an integration perspective. So, there are some API initiatives and cloud initiatives.”
“API management is becoming more mainstream. You can look at various analyst reports where they have started talking about event brokering as a mechanism for you to become real-time and going to cloud is offcourse an interesting option.”
The concept called event mesh, especially for large distributed systems would become a mechanism to move your data in a smooth manner. Interactions would be more asynchronous.
During his presentation, Puri spoke about the role of Event Mesh and its significance.
What is Event mesh?
An event mesh is a configurable and dynamic infrastructure layer for distributing events among decoupled applications, cloud services and devices. It enables event communications to be governed, flexible, reliable and fast. An event mesh is created and enabled through a network of interconnected event brokers.
In other words, an event mesh is an architecture layer that allows events from one application to be dynamically routed and received by any other application no matter where these applications are deployed (no cloud, private cloud, public cloud). This layer is composed of a network of event brokers.
How is “event mesh” different from service mesh?
Event mesh complements service mesh. It is a layer parallel to service mesh and completes the application architecture by providing the full set of inter-application communication patterns: service mesh for RESTful and general request/reply interactions; event mesh for asynchronous, event-based interactions. Refer to the layering diagram below for the position of each in an application stack.
A service mesh is a configurable infrastructure layer for microservices applications that makes communication flexible, reliable and fast. It is promoted by giants in the industry such as Google, Microsoft, IBM, Red Hat, Pivotal and others and is now included with Kubernetes, OpenShift, and PKS by Istio/Envoy. The data plane portion (i.e., Envoy) is implemented through a sidecar proxy and provides:
- Service discovery
- Load balancing
- Authentication and authorization
- Circuit breaker support
Both meshes are similar in that they enable better communication between applications by putting certain functions into a layer between the network and the application. However, there are a few important distinctions:
- Service mesh connects microservices in cloud environments – Kubernetes only today – with the promise of enabling this communication between different Kubernetes clusters and perhaps other clouds in the future.
- Event mesh connects not only microservices but also legacy applications, cloud-native services, devices, and data sources/sinks and these can operate both in cloud and non-cloud environments. An event mesh can connect any event source to any event handler.
What are the core capabilities of an event mesh?
The generic capabilities of an event mesh:
- A network of interconnected event brokers that can be deployed in any cloud, PaaS or non-cloud (so it includes all capabilities of an event broker but is distributed)
- Provides dynamic distribution of events so that event consumers can receive events from any event producer, no matter where the producer and consumer are attached to the mesh, without the need for configuration of event routing
In other words, an ‘event mesh’ is:
- inherently ‘event-driven;’
- created by connecting event brokers;
- environment agnostic (can be deployed anywhere); and,