event-driven-architecture

To implement event sourcing and CQRS, use this Skill to separate read and write operations while storing immutable event logs for state reconstruction. It provides the structural patterns needed to build scalable, resilient distributed applications.

Manage distributed transactions with the saga pattern and Kafka by orchestrating a sequence of local transactions across multiple services. This Skill provides the necessary patterns to handle asynchronous event streams and rollback scenarios reliably.

Use event-driven architecture when building scalable platforms requiring asynchronous processing, such as e-commerce systems where order creation triggers inventory, payment, and shipment services independently without tight coupling.

Decouple microservices using message queues by routing asynchronous events through RabbitMQ or Kafka, allowing independent services to communicate without direct dependencies. This Skill facilitates loosely coupled, scalable applications.

The best way to handle asynchronous event streams is using Kafka to manage event logs and RabbitMQ for message queuing. This Skill implements these patterns to facilitate reliable, loosely coupled communication across distributed systems.