Ac Message Queues

The middleware layer that decouples producers from consumers: broker topologies and what a direct, fanout, or topic exchange actually routes, delivery guarantees from at-most-once through to effectively-once, acknowledgement and redelivery when a consumer dies mid-message, poison messages and the dead-letter path, priority and fair dispatch, queue backpressure and bounded buffers, competing consumers and ordering under scale-out, and the written queue record. It explains how a queue behaves and where it fails; it never recommends a broker. Use when asking "message queue", "dead letter queue", "poison message", "ack and redeliver", "competing consumers", "fanout exchange", "topic routing", "work queue", "priority queue", "why did this message arrive twice", "prefetch". Not for event-driven design between your own services (ac-event-driven-architecture), not for webhook delivery to endpoints you do not own (ac-webhook-and-async-delivery), not for durable workflows and sagas (ac-durable-execution).

jiayaoqijia Updated 81 repo stars

File contents

jiayaoqijia/cryptoskill commit cb5c5666af

Frequently asked questions

npx get-skill add jiayaoqijia/ac-message-queues