MessageQueues
Async, decoupled communication via a queue (SQS, RabbitMQ, Kafka) — producer doesn't wait for consumer.
Why we need this / what value this brings
Decouples the producer's success from the consumer's immediate availability — the producer doesn't need the consumer to be up right now.
When to use this
When an operation can complete asynchronously (sending a notification) rather than needing an immediate result.
How to use or implement this
Push a message onto the queue at the trigger point; have a separate worker consume it with its own retry/dead-letter handling.
Subtopics
Research questions
- Does Localz need a queue yet, or is synchronous request/response still sufficient at current scale?
Empty folder — drop notes, links, and findings here as you research.