Message Queuesv1.0.0

An e-commerce platform needs to decide between Kafka, RabbitMQ, or SQS for handling order events. The workflow guides through delivery semantics, partitioning, and idempotency to ensure orders are processed exactly once without duplicates.

A fintech company experiences increasing consumer lag and DLQ growth in their transaction processing system. The skill helps diagnose hot partitions, retry strategies, and backpressure to restore throughput and reliability.

A healthcare provider needs to guarantee that duplicate claim messages do not result in double billing. The workflow designs at-least-once delivery with idempotent handlers and versioned message contracts.

A media company moves from RabbitMQ to Kafka to support higher throughput and partitioned ordering. The skill covers topology design, partition key selection, and rebalance handling for live streaming data.

A SaaS provider needs consistent database writes and queue publishes to avoid dual-write failures. The workflow introduces the transactional outbox pattern and failure drills to validate idempotency.

Offer expert consulting to design and implement queue systems tailored to client workloads. Includes delivery semantics, partitioning, and failure drills for enterprise clients.

Provide ongoing monitoring, lag alerts, and capacity planning for clients' message queues. Includes DLQ management and replay tooling as a service.

Conduct audits of existing queue systems to identify risks (duplicates, reordering, poison messages) and train teams on best practices. Includes failure drill facilitation.