messaginglisted

# Messaging Skills ## Overview Asynchronous communication patterns for building scalable, decoupled distributed systems. Messaging enables services to communicate without direct coupling, improving reliability and scalability. ## Messaging Types | Type | Description | Use Case | Examples | |------|-------------|----------|----------| | **Point-to-Point** | One sender, one receiver | Task distribution | RabbitMQ, SQS | | **Pub/Sub** | One sender, many receivers | Event broadcasting | Kafka, Redis Pub/Sub | | **Request/Reply** | Synchronous over async | RPC-style calls | RabbitMQ RPC | | **Event Streaming** | Ordered, replayable log | Event sourcing | Kafka, Kinesis | ## Delivery Guarantees | Guarantee | Description | Trade-off | |-----------|-------------|-----------| | **At-most-once** | Fire and forget | May lose messages | | **At-least-once** | Retry until acknowledged | May have duplicates | | **Exactly-once** | Deduplicated delivery | Complex, higher latency | ## When to Use Messaging ### Use Messaging For - Decoupling services - Async task processing - Event-driven architectures - Load leveling and buffering - Cross-service communication ### Avoid Messaging When - Simple request/response is sufficient - Strong consistency is required - Real-time response is critical - System complexity isn't justified ## Categories ### Fundamentals Core messaging concepts: - **Messaging Patterns** - Common communication patterns - **Sync vs Async** - When to use each approac