Back to tags
Tag

Agent Skills with tag: event-sourcing

7 skills match this tag. Use tags to discover related Agent Skills and explore similar workflows.

cqrs-event-sourcing

CQRS and Event Sourcing patterns for scalable, auditable systems with separated read/write models. Use when building audit-required systems, implementing temporal queries, or designing high-scale applications with complex domain logic.

cqrsevent-sourcingscalabilityaudit-trails
NickCrew
NickCrew
52

event-driven-architecture

Event-driven architecture patterns with event sourcing, CQRS, and message-driven communication. Use when designing distributed systems, microservices communication, or systems requiring eventual consistency and scalability.

event-driven-architectureevent-sourcingCQRSmessage-driven
NickCrew
NickCrew
52

kurrentdb

Provides KurrentDB (EventStoreDB) client code for event sourcing and CQRS. Generates correct package names, connection strings, and API patterns for Python, Node.js, .NET, F#, Go, Java, Rust. Triggers on "kurrentdb", "eventstore", "event sourcing", "append events", "read stream", "subscription", "aggregate", "CQRS".

event-sourcingcqrseventstorepython
kurrent-io
kurrent-io
1

event-driven

Production-grade event-driven architecture skill for Kafka, RabbitMQ, event sourcing, CQRS, and message patterns

event-driven-architecturekafkarabbitmqevent-sourcing
pluginagentmarketplace
pluginagentmarketplace
1

design-patterns

Game server design patterns including ECS, command pattern, and event sourcing

design-patternsecscommand-patternevent-sourcing
pluginagentmarketplace
pluginagentmarketplace
2

event-driven

Event-driven architecture patterns including message queues, pub/sub, event sourcing, CQRS, and sagas. Use when implementing async messaging, distributed transactions, event stores, command query separation, RabbitMQ, Kafka, SQS, or NATS integration.

pub-submessage-queueCQRSevent-sourcing
cosmix
cosmix
3

event-sourcing

Implement event sourcing and CQRS patterns using event stores, aggregates, and projections. Use when building audit trails, temporal queries, or systems requiring full history.

event-sourcingCQRSevent-driven-architectureaudit-trails
aj-geddes
aj-geddes
301