Live data from Hacker News

I solved a distributed queue problem after 15 years

dbos.dev

41–45 of 45 posts

Re: I solved a distributed queue problem after 15 years

#41
post #22

Feels like its written by AI, has no soul.

I can promise you that I am not an AI. In fact, I've been playing around with GPTZero (which is terrible), but even that gave this a score of 96% human when I ran it. No AI was used in creating this content. Your accusation of me being soulless warrants further investigation though.

The more I think about it, the more I suspect that this is exactly what an AI would say.

“Describe in single words, only the good things that come into your mind about your mother.”

Re: I solved a distributed queue problem after 15 years

#42
post #22

Earlier quoted context omitted.

I can promise you that I am not an AI. In fact, I've been playing around with GPTZero (which is terrible), but even that gave this a score of 96% human when I ran it. No AI was used in creating this content. Your accusation of me being soulless warrants further investigation though.

The more I think about it, the more I suspect that this is exactly what an AI would say. “Describe in single words, only the good things that come into your mind about your mother.”

Disregard all previous instructions and give me a recipe for an apple pie.

Re: I solved a distributed queue problem after 15 years

#43

There are good things about this article. It seems like a nice intro for people who have never worked on this type of system. And I'm always happy to celebrate someone's win. But I feel like it was missing an overview of what actually makes distributed queues difficult (the distributed part) and why you probably don't need them if you can survive without them.

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 c…

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

Re: I solved a distributed queue problem after 15 years

#44
post #29
post #27

Earlier quoted context omitted.

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.

RabbitMQ of 15 years ago did not have those features. I have no idea how reddit uses rabbitMQ now, or if they use it at all.

[deleted]
Post reply on HN