Hacker News Reader

Development seems pretty rapid, how often are breaking changes forcing workflow modifications to keep updated with the latest versions?

View on HN

We keep all workflows running on Sim cloud backwards compatible always. The idea is that you build, deploy, and never have to make modifications again unless you want to.

If we release a breaking change that requires a migration for existing local workflows, we release notice at least a few weeks ahead of time/bake it into the db migrations.

Incase there are significant changes made, everything is versioned so you opt-in to upgrading.

Thanks, and that sounds great. On the backend what are you using for the DAG stuff to make it durable? Temporal?

We actually wrote our own serializer & execution engine and for long-running jobs, we defer to trigger.dev

Reply on news.ycombinator.com