(ex temporal employee) believe it or not this is SIMPLER than temporal's actual workers. what you're seeing is a "DBOSify worker" embedded in each application server, which is not the same thing as temporal's conception of workers (which are separate from the app server). i havent spent much time with dbosify but i'd say this is closer to a "second client" than a full worker... just a terminology issue

I think "without needing any infrastructure" is in contrast to Temporal, which has its own server in front of the storage.

I asked the DBOS folks about this before; the idea is that there is no "coordination node", only the workers and the DB. See DBOS folks previously: https://news.ycombinator.com/item?id=45186494

Hi! Do you have an example that includes a full agent workflow?

You can add a dev dependency in your pyprojec.toml with uv, look it up.

What would it involve to get DBOSify for C#?