Services/MessageQueuing
< Services
Jump to navigation
Jump to search
Planning Questions
Trade-offs of MQ implementations
- Levels of durability, and their throughput characteristics
- Prioritization of messages
- Out of band task vs. remote actor
What is the simplest MQ system and features to add from there?
- Put a single message on a queue for later retrieval in a FIFO manner, non-persistent
- Transient messages (Semi-durable, higher throughput at the possible loss of some recent messages in a crash)
- Persistent messages (Accessible until consumed)
- Prioritizing of messages? Or allow for multiple queues and have the client prioritize where it pulls messages from?
Apps should be able to create both durable and temporary queues on-demand, as well as assign a TTL to a queue for temporary use.