event-driven-architecture

Implement sagas with compensation using this skill's resilient patterns for distributed transactions. It provides retry mechanisms and observability hooks to maintain data consistency across microservices without two-phase commits.

Yes, you can swap Kafka for Redis or cloud brokers without code changes. The skill provides a broker abstraction layer that decouples your event-driven microservices from specific message broker implementations.

Maintain read models using CQRS and event sourcing by utilizing the skill's command and query buses. It handles event projections to automatically update read-models via continuous event streams.

Yes, it supports Dapr integration for Kubernetes deployments. The skill provides guidance on utilizing Dapr's state store, pub/sub, and service invocation bindings, including sample manifests for cloud-native deployment.

Handle schema evolution for versioned events using the skill's framework-agnostic event patterns. It supports versioning and a generic event store to ensure backward compatibility as your event-driven architecture scales.

Avoid event-driven architecture when strict real-time consistency is required over eventual consistency. If your system cannot tolerate saga compensation latency or complex event schema evolution, synchronous patterns may be better.