Tag Archives: Event-Driven Architecture

Amazon SNS: Part 1 – Introduction for Developers and Architects

Dive into the core functionalities of Amazon SNS (Simple Notification Service), a cornerstone for enabling real-time and event-driven architectures in cloud computing. Understand how SNS facilitates seamless communication between applications through its pub/sub messaging model, allowing for broad-scale message distribution to various subscribers. Explore the service’s key features, including multi-protocol support, high throughput, message filtering, and integration within the AWS ecosystem, and learn how it ensures secure, scalable, and efficient messaging across diverse applications.

Overview of Communication Patterns: Event-Driven, Message-Driven and Request-Driven

Dive deep into the intricate world of communication patterns in system architecture. Explore the strengths and trade-offs of request-driven, message-driven, and event-driven models, and how they shape the interaction, scalability, and resilience of modern applications. Unravel the complexities and operational dynamics that can make or break your system’s architecture.

What is event driven? The five types of event-driven architecture

Event-driven architecture is an approach to software design that relies on events to trigger actions. There are five primary patterns of event-driven architecture, including event-notification, event-carried state transfer, CQRS (Command Query Responsibility Segregation), event-sourcing, and event-streaming.
In the article I will describe what they are and the difference between Event-Streaming and Event-Sourcing

How to ensure events are processed in order when retrying events out of sequence (when using event platforms like Apache Kafka)

In the post, How to handle retry messages and failures when using event streaming platforms like Apache Kafka, I walked through how to retry events when using Apache Kafka.  Now in this post, I will discuss an approach you can implement to ensure processors process events in order even when you’ve implemented a retry solution.  YouTube video After… Read More »

The Outbox Pattern: The guaranteed event publishing pattern

What is the outbox pattern? It is when a request or the event processor performs its database transaction operation but does not publish the occurred event afterwards. Instead, during the database transaction, a record or multiple records are inserted into a dedicated database table, the outbox table, which holds the records which you want to publish to a… Read More »