3 ms·
What if the queue goes down? Without insane engineering, there is always going to be a single point of failure somewhere.
by 0cf8612b2e1e 4y ago
What if the queue goes down? Without insane engineering, there is always going to be a single point of failure somewhere.
- Spivak 4y agoIt doesn't, it's two clusters in replication. It's like the least insane engineering? Are y'all not running your stuff highly available?
- wvenable 4y agoDatabases run as clusters in replication...
- Spivak 4y agoYes? I don't understand your point. Queueing systems are a kind of database with different semantics and performance characteristics. The answer to what happens if the queue goes down is that it runs highly available.
- wvenable 4y agoMost people don't need another kind of database. A few do but not enough to justify an "everyone should do it this way by default" opinion.
- Spivak 4y agoSure, if you're at the "it's not worth maintaining two dbs or paying for any managed offering" stage then you should still use the pattern but implement the work queue in your primary db. It'll be slower and you'll have to diy a little if there aren't ready made libs to do it but you still get all the major benefits.