3 ms·
My initial thought when opening your website was that this was a job queue, like BullMQ. Not a "link things together like IFTT/Zapier/N8N but in code" platform.
by louis-lau 3y ago
My initial thought when opening your website was that this was a job queue, like BullMQ. Not a "link things together like IFTT/Zapier/N8N but in code" platform. I don't think I'd use "Background Jobs framework" to describe what you're building, as that term has very different associations. Am I right in saying this is like BullMQ, except with integrations? If so, I'd focus more on the integration part of your marketing.
- matt-aitken 3y agoThat's really interesting. What associations do you have with "Background Jobs framework"? Quite a lot of our customers are using us instead of Temporal. Not for linking stuff together use cases.
- nsonha 3y agoTemporal calls itself a “Durable execution platform”, which I think emphases the persistence aspect of a message queue. I remember Cadence which is Temporal’s predecessor called itself a “workflow orchestration framework”. I think it’s a better term.
- louis-lau 3y agoJust a background job queue library basically. Maybe with a fancy dashboard. That was my first impression.