skills.rest
somachak
somachakCOMMUNITY
Explore all skills by this author →
GitHub

building-event-driven-services

Design event-driven microservices with contracts, broker selection, and delivery semantics.

Updated Apr 14, 2026
Search Tags:#messaging#architecture#event-driven#kafka#outbox#domain-events#consumer-isolation
One-click install
npx skills add https://github.com/somachak/claude-code-skills-db --skill building-event-driven-services
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: building-event-driven-services
Source: https://github.com/somachak/claude-code-skills-db/tree/main/skills/backend/building-event-driven-services
Command: npx skills add https://github.com/somachak/claude-code-skills-db --skill building-event-driven-services

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Event-driven service design helps teams decouple services, enable asynchronous communication, and improve resilience using message brokers, streams, and domain events.

Core Features & Use Cases

  • Guidance on contracts, delivery semantics, replay handling, and consumer isolation for event-driven architectures.
  • Decision frameworks for brokers (Kafka, RabbitMQ, AWS SNS/SQS) and patterns like outbox and event sourcing.
  • Real-world scenarios: order pipelines, audit logs, and real-time analytics.

Quick Start

Define the event-driven service contracts, select a suitable broker, and implement basic event publishing and consumption workflows.

Frequently Asked Questions about building-event-driven-services

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decouple tightly coupled microservices using event-driven architecture?▼

The outbox pattern ensures reliable event publishing by writing events to a database table within the same transaction as domain state changes. This guarantees atomicity, preventing data inconsistency between your service database and message broker.

What is the best way to handle event replay and idempotent processing in Kafka consumers?▼

Handle event replay and ensure idempotent processing by designing consumers to safely reprocess duplicate messages. You must enforce explicit contracts and implement delivery semantics that tolerate redelivery without causing side effects or data corruption.

When should I choose Kafka over RabbitMQ or AWS SNS/SQS for an event-driven service?▼

Choose Kafka for high-throughput event streaming and replay capabilities, while RabbitMQ or AWS SNS/SQS suit complex routing and transient messaging. Evaluate broker selection frameworks based on your specific scalability and delivery semantic requirements.

How do I implement consumer isolation across microservices to prevent cascading failures?▼

Implement consumer isolation by decoupling message consumption logic from downstream processing using separate broker queues or consumer groups. This prevents slow or failing consumers from blocking producers and causing cascading system failures.

Does event-driven design work for building order pipelines and real-time analytics?▼

Event-driven design works effectively for order pipelines, audit logs, and real-time analytics. By leveraging domain events and stream processing, you can asynchronously route data across services while maintaining a resilient, scalable architecture.

Related Skills

Explore More Software Engineering Skills→
yairbedermanyairbederman

microservice-architect

Plan microservice architectures with domain-driven design and service boundaries.

Community
Advanced
rnavarychrnavarych
14

role-backend:message-queues

Implement message queue systems with RabbitMQ, Kafka, Redis Streams, SQS, and Pub/Sub.

Community
Advanced
williamzujkowskiwilliamzujkowski
6

Kafka Messaging Architect

Design Kafka architectures with exactly-once semantics and Schema Registry.

Community
Advanced
vincent119vincent119

go-domain-events

Design Go domain events with an event bus and outbox-based publishing.

Community
Advanced