4 ms·
I searched all over the web for a reliable and scalable plain message queue that could work in a full disk-backed mode, not requiring the data to fit in memory.
by synchrone 6y ago
I searched all over the web for a reliable and scalable plain message queue that could work in a full disk-backed mode, not requiring the data to fit in memory.
Was very impressed with how little RAM and CPU it consumed under load.
- NicoJuicy 6y agoDid you check out NATS?
- tapirl 6y agoBoth nsq and nats are very memory saving.
- synchrone 6y agoWas using it in production before. NATS itself is great and reliable. However disk persistency is done with nats-streaminh and i had big issues with it's Raft file based store, where it would stop accepting messages after a short network issue, and not get unstuck unless I destroy the whole nats-streaming data storage amd start from scratch. Also raft means 3x disk usage for one queue, since its fully replicated
- polskibus 6y agoDoes it offer any delivery guarantees?
- synchrone 6y agoAs far as I read the docs, if you use 0 for memory storage size - it will flush to disk before responding that the message was published OK. Delivery is "at least once".