Conversation

Why don't all backend runtimes/frameworks fundamentally start with a queueing system? Start with a persistent queue as source of truth. all computation is done in workers that pop off a queue and/or add to it. Has this been tried and failed somehow? is this like Elixir?
77
409
Trying this now with :) PSA even though you start with a queue you can still block until your work is done, aka "synchronous start" of a workflow
Quote Tweet
I'm excited to finally share why I've joined @temporalio as Head of Developer Experience! Here's my explainer on 3 core opinions of Temporal, why they're hard to do well, and the business opportunities it presents: swyx.io/why-temporal/
Show this thread
1
7
From reading the docs, it seems to run your code and actions that have already completed with cached values. It stops at the first unresolved action, which is queued to run. When that finishes it runs the workflow again and repeats until it’s all done.
1
1
So that’s how you can have tasks that sleep for multiple days while the system it still scales. And you don’t have to think about queuing and so on in your workflow of you don’t want to. Quite elegant, if I understand it correctly.
1
1
this writeup is probably written below your level but the resources at the end may help. would love to hear your thoughts/questions!
Quote Tweet
I'm excited to finally share why I've joined @temporalio as Head of Developer Experience! Here's my explainer on 3 core opinions of Temporal, why they're hard to do well, and the business opportunities it presents: swyx.io/why-temporal/
Show this thread
1