Have you done iron infusions? My wife has to get these once in a while. She had gastric surgery years back and has issues with absorption of oral supplements.
The job will run the next time a worker runs (in both cases).
And doesn’t that mean the job potentially runs twice? Yes.
In DBOS there are two kinds of “things that run”: workflows, and steps (workflows are made of steps).
Workflows must be deterministic (so it’s fine if it runs twice). Steps don’t have to be deterministic but have at-least-once execution (so it’s best if these are idempotent).
This is ironic. They didn’t say they believe. You offered your belief that you know something that happened long ago (extraordinary claim), and they are naturally curious how you could know that. If you’re a time traveler or whatever we’d be quite interested to hear more.
One difference is, when the business hits a tough patch, the bank starts asking questions, and whether or not the bank lets it all continue depends primarily on whether there’s a CEO/CFO who:
- Has history with the bank (trust)
- Is willing to put their neck on the line
AI in the current form has no ability to put its neck on the line.
DBOS is much less complexity compared to Temporal. That’s the benefit.
Main tradeoff is lower performance. Or at least, you’re going to be limited to what you can push through Postgres. If that’s sufficient for your needs DBOS is great.
> we are transferring value from our current standard of living to pay for retirement checks
Isn’t this just what happens when you have an inverted pyramid (older population is larger than the younger population)?
> One can argue that PEs make the business more efficient
I’ve never seen it (I agree with you). To improve something they’d have to understand the business and do a bunch of work. Mostly they show up at quarterly meetings and want spreadsheets that measure some number that will go up (regardless if that number means anything).