Event Driven Architecture (EDA) is an architectural pattern where publishers and subscribers (aka producers and consumers) are decoupled and connected by a mesh of event brokers. This allows for data and events to be published from one location for use across the organization. Because it is technology agnostic it enables event-driven integration of different applications and functions. There is a lot of functionality required in event brokers, including multiple pub/sub patterns, tools for different client consumption rates, variability of subscribers, guaranteed messaging, autoscaling, partitioning, and more.OpenTelemetry has quickly grown to be one of the most popular CNCF projects of all time with support from across the landscape of Application Performance Monitoring, and related sectors. It has helped “observability” to make its way into enterprise planning because it enables an end-to-end look at both performance and system state, where before distributed tracing, the focus could only be on operational metrics like, up-time and speed.The challenge of observability as it applies to EDA is that the complex functionality in an event broker can be a black box – meaning that they aren’t part of the solution. However, a well instrumented system can enable architects, middleware managers, and developers to ensure that they have observability into these systems.This short webinar will delve into EDA and OpenTelemetry and how they come together to help with debugging, troubleshooting, analytics, and data lineage. It includes a reference to, and link for, the OpenTelemetry demo; as well as where to get a Git covering two commonly used broker types.
Presented by: solace