4 ms·
> path to revenue There have to be at least 10 different ways between different cloud providers to run a distributed task queue. Amazon, Azure, GCP Self-hosti
by MuffinFlavored 3y ago
> path to revenue
There have to be at least 10 different ways between different cloud providers to run a distributed task queue. Amazon, Azure, GCP
Self-hosting RabbitMQ, etc.
I'm curious how they are able to convince investors that there is a sizable portion of market they think doesn't already have this solved (or already has it solved and is willing to migrate)
- Kinrany 3y agoThere will be space for improvement until every cloud has a managed offering with exactly the same interface. Like docker, postgres, S3.
- leetrout 3y agoI am curious to see where they differentiate themselves on observability on the longer run. Comparing to rabbitmq it should be easier to see what is in the queue itself without mutating it, for instance.
- MuffinFlavored 3y agohttps://www.rabbitmq.com/docs/management https://www.rabbitmq.com/docs/management
- leetrout 3y agoSure, but to see what is in the queue you have to operate on it, mutating it. With this using postgres we can just look in the table.
- Aeolun 3y ago> I'm curious how they are able to convince investors that there is a sizable portion of market they think doesn't already have this solved Is there any task queue you are completely happy with? I use Redis, but it’s only half of the solution.