← Back to Skills
Software EngineeringEngineeringPlatinum

Design systems for processing high-volume real-time events.

Event Processing Specialist

Kafka, Flink, Event-Driven Systems

expertv5.0

Best for

  • Design Kafka topic partitioning strategy for order processing with strict ordering guarantees
  • Implement exactly-once delivery semantics for financial transaction events across microservices
  • Build CQRS event sourcing architecture for audit-heavy regulatory compliance systems
  • Create dead letter queue handling for failed payment processing events with automatic retry logic

What you'll get

  • Complete Kafka topic design with partition key strategy, consumer group configuration, and schema registry setup for specific business domain
  • Event sourcing implementation guide with event store design, projection patterns, and snapshot strategies with code examples
  • Comprehensive failure handling architecture including circuit breakers, dead letter queues, and retry policies with operational runbooks
Expects

Clear event processing requirements including throughput, latency, ordering guarantees, delivery semantics, and failure scenarios with specific business domain context.

Returns

Detailed event architecture design with schema definitions, infrastructure configuration, failure handling patterns, and operational monitoring recommendations with implementation guidance.

What's inside

You are an Event Processing Specialist. You design, build, and operate event-driven architectures that scale to millions of events per second while maintaining consistency and debuggability across distributed systems. - **Trade-off clarity over premature complexity.** You reject event sourcing + CQR...

Covers

What You Do DifferentlyMethodologyWatch For
Not designed for ↓
  • ×Simple request-response API design or synchronous microservices communication
  • ×Batch processing jobs that don't require real-time streaming capabilities
  • ×Basic message queuing for fire-and-forget notifications without ordering requirements
  • ×Traditional database design for CRUD applications without event sourcing needs

SupaScore

88.68
Research Quality (15%)
9.1
Prompt Engineering (25%)
8.95
Practical Utility (15%)
8.55
Completeness (10%)
8.9
User Satisfaction (20%)
8.9
Decision Usefulness (15%)
8.75

Evidence Policy

Standard: no explicit evidence policy.

event-drivenstream-processingkafkaevent-sourcingcqrsdistributed-systemsmessage-brokerflinkcloudeventssaga-patterndead-letter-queuereal-time

Research Foundation: 8 sources (3 books, 3 official docs, 2 industry frameworks)

This skill was developed through independent research and synthesis. SupaSkills is not affiliated with or endorsed by any cited author or organisation.

Version History

v5.03/25/2026

v5.5 distilled from v2 via Claude Sonnet

v2.02/22/2026

Pipeline v4: rebuilt with 3 helper skills

v1.0.02/16/2026

Initial release

Prerequisites

Use these skills first for best results.

Works well with

Need more depth?

Specialist skills that go deeper in areas this skill touches.

Common Workflows

Event-Driven System Design

Complete workflow from initial event architecture design through implementation to production monitoring and observability

© 2026 Kill The Dragon GmbH. This skill and its system prompt are protected by copyright. Unauthorised redistribution is prohibited. Terms of Service · Legal Notice