← ClaudeAtlas

event-driven-architecturelisted

Generic Event-Driven Architecture patterns with Kafka, Dapr, and modern messaging systems. Provides reusable patterns for building scalable, resilient event-driven microservices. Framework-agnostic implementation supporting multiple message brokers, state stores, and event patterns. Follows 2025 best practices for distributed systems.
aiskillstore/marketplace · ★ 329 · AI & Automation · score 82
Install: claude install-skill aiskillstore/marketplace
# Event-Driven Architecture with Modern Patterns This skill provides comprehensive patterns for implementing event-driven microservices using modern messaging systems, distributed runtimes, and cloud-native patterns. It's designed to be framework-agnostic and applicable to any domain requiring event-driven capabilities. ## When to Use This Skill Use this skill when you need to: - Build event-driven microservices architecture - Implement pub/sub patterns with Kafka, RabbitMQ, or cloud services - Use Dapr for distributed application patterns - Implement real-time notifications and workflows - Build recurring task and reminder systems - Create audit trails and activity logs - Implement distributed state management - Build serverless event workflows - Handle event sourcing and CQRS patterns ## 1. Core Event Architecture ### Base Event Schema ```python # events/core.py from pydantic import BaseModel, Field, validator from datetime import datetime from typing import Optional, Dict, Any, Union, List from enum import Enum from abc import ABC, abstractmethod import uuid import json class EventVersion(str, Enum): """Event versioning support""" V1_0 = "1.0" V1_1 = "1.1" V2_0 = "2.0" class EventPriority(str, Enum): """Event priority levels""" LOW = "low" NORMAL = "normal" HIGH = "high" CRITICAL = "critical" class BaseEvent(BaseModel, ABC): """Base event schema with common fields""" # Core identification event_id: str = Field(defau