3 ms·
Current company's infrastructure is currently all on AWS, so using Step Functions. However I really _really_ like temporal.io's code-first solution (just didn't
by jekude 5y ago
Current company's infrastructure is currently all on AWS, so using Step Functions. However I really _really_ like temporal.io's code-first solution (just didn't want to self-host).
Perhaps the dust on best practices / tech for workflows or sagas just hasn't settled yet to include in a framework like the one I am envisioning.
In general I think Supabase is fantastic in terms of the interoperability of all of the features they introduce. Just waiting on functions (and perhaps events / queues for async communication).
- swyx 5y agoah nice! make sure to fill out our waitlist if you want our managed service: https://temporal.io/cloud https://temporal.io/cloud meanwhile if you like workflows as code and want to stay in the AWS world what about AWS SWF? our CEO used to be tech lead of that and it shares similar ideas. yeah we are hoping to establish what best practice/architecture for workflows looks like. Feedback/questions welcome: https://docs.temporal.io/blog/workflow-engine-principles https://docs.temporal.io/blog/workflow-engine-principles
- jekude 5y agoam an ex-AWS engineer who worked on a service team that depends on SWF and also on one that depends on Step Functions. IMO the serverless-ness (?) of Step Functions and not having to manage pollers like SWF is huge.
- swyx 5y agoyeah we hear that a bunch. long term we'll host pollers. gotcha tho :) thanks for the thoughts