Event-Driven Architecture - technical questions

Apache Kafka is an open-source distributed streaming platform developed by the Apache Software Foundation. It is designed to handle real-time data feeds and stream processing with a high level of scalability, fault-tolerance, and reliability. Kafka is commonly used for building event-driven architectures and processing large volumes of data streams in real-time.

It is not. Though an event hub such as Kafka is an essential component in an Event-Driven architecture.

An event hub / event broker is a distributed event streaming platform for high-performance data pipelines, streaming analytics, data integration, and mission-critical applications. It is an essential component in an Event-Driven Architecture.

An event hub does not allow you to define business logic on the cluster, which means it is a purely technical component and not the same as an ESB. This eliminates the need for a separate ESB team. By using an event hub business logic is always handled in the component that is responsible of the business domain, which has obvious benefits for maintainability and scalability.

An event is anything that happens in a business environment or their customers’ ecosystem.
The applications and services that trigger events are called event producers. Producers know when certain events occur and publish them to show that they happened while including the relevant information.

The event hub receives the notifications sent out by producers and notify other parties that have registered their interest in receiving certain events. Those interested parties are called event consumers. They can be organised in consumer groups by the type of events they are interested in.

RedPanda is a simple, powerful, and cost-efficient streaming data platform that is compatible with Kafka® APIs. It is built to deliver GB/s+ throughput and lower average latencies. RedPanda offers a fully-managed cloud service or self-hosted platform.