Thanks! DBOS is simpler not because it ignores complexity, but because it uses Postgres to deal with complexity. And Postgres is a very powerful tool for building reliable systems!
Temporal has the option of using postgres as the persistence backend. Presumably, the simplicity of DBOS comes from not having to spin up a webserver and workflow engine to orchestrate the functions?
Have you had scalability issues because your tables got too big?
Is there a mechanism to GC workflows that are completed?
Tables getting too big hasn't been a concern in practice because information on completed workflows can easily be GC'ed.