The Design of an Event Store - The topics “event-driven architecture” “event stream processing” and “event sourcing” have enjoyed quite a buzz as of late.
The topics “event-driven architecture” “event stream processing” and “event sourcing” have enjoyed quite a buzz as of late. While the concepts are not new, it would seem that only now the software engineering community is beginning to appreciate the power and flexibility of building autonomous, loosely coupled systems that intelligently react to events, rather than being told what to do.
Now that our industry has gotten on board the event-driven bandwagon, some of us are starting to look beyond our usual building blocks — Kafka, Pulsar, and NATS Streaming — to address the concerns of long-term persistence and intelligent retrieval of events. We are, of course, talking about an event store.
When contemplating event stores, the first question we should ask ourselves is: what exactly is an event store?
As it stands, a canonical definition of an event store does not exist… yet. Everyone has a different understanding of what an event store ought to do, although most practitioners have come to agree that an easily queryable, long-term persistent store of event records is probably in order, given our ongoing investment into this architectural paradigm.
A “store of event records” hardly sounds convincing on its own. Realistically, something as straightforward as this could easily be accomplished with a database, or even Kafka itself. (And other event streaming platforms, for that matter.) Ostensibly, practitioners wouldn’t have coined a term unless it stood on its own merit. So, we turn our attention to the “queryable” part.
Some of the main challenges that monolith applications face are having low availability and handling service disruptions. This is where…
This Apache Kafka Tutorial - Kafka Tutorial for Beginners will help you understand what is Apache Kafka & its features. It covers different components of Apache Kafka & it’s architecture. You'll learn: What is Kafka? Kafka Features, Kafka Components, Kafka architecture, Installing Kafka, Working with Single Node Single Broker Cluster
Event-Driven Microservices with Apache Kafka®, Kotlin, and Ktor | Microservice applications often change communication protocols between services from request-response to event streaming. Apache Kafka® is a great choice for addressing the challenges of building high-load applications at scale. This session will provide an introduction on how to use Kotlin and Ktor to build an application that shares geographical coordinates among clients. Anton will give an introduction to Ktor, the Kotlin framework for building connected applications. After that, Viktor will demonstrate how event streaming works with Kafka, and he will identify the other features the platform provides for scaling the solution.
Apache Kafka is an open source distributed streaming platform that allows you to build applications and process events as they occur. Kafka is a Publish-Subscribe based messaging system that is exchanging data between processes, applications, and servers. Applications may connect to this system and transfer a message onto the Topic(we will see in a moment what topic is) and another application may connect to the system and process messages from the Topic.
Learn Apache Kafka in 5 minutes. Learn the principles of Apache Kafka and how it works through easy examples and diagrams! What is Kafka? Kafka Features. Kafka Components. Kafka architecture. Installing Kafka. Why Learn Apache Kafka?