| ▲ | chatmasta 3 days ago | ||||||||||||||||||||||
Am I missing something or did the article never address the title? > How I solved a distributed queue problem after 15 years Well… how? The post is a nice description of durable queues, but it never explicitly says they’re a solution to a distributed queue problem, nor does it specifically define such a problem. Is “durable queue” a brand name of a DBOS feature? Because the post doesn’t even say “and here’s how you can use DBOS for durable queues,” nor does it compare it to Kafka or any other “durable queue” solution that’s emerged in the fifteen years since the author used RabbitMQ… (btw, isn’t RMQ a durable queue…?) | |||||||||||||||||||||||
| ▲ | rancor 3 days ago | parent | next [-] | ||||||||||||||||||||||
Not only is RabbitMQ durable, it has transactions with rollback. The entire set of problems the author describes are down to Reddit using Rabbit like Redis. | |||||||||||||||||||||||
| |||||||||||||||||||||||
| ▲ | nchmy 3 days ago | parent | prev [-] | ||||||||||||||||||||||
Came to say this as well. I was excited for a deep dive into a difficult problem, and only found an enormously superficial article that didnt even mention the title. Very disappointing. Like Reddit edit: I now see that its not a personal blog, but actually just a fluff piece for a company blog. If they had actually gone into detail about the problem, and how the service they offer solves it easily, it would have been fine | |||||||||||||||||||||||