3 ms·

For people who are building durable workflows. You should definitely checkout temporal [1]. It is production ready, you can implement pretty much same using the

For people who are building durable workflows. You should definitely checkout temporal [1]. It is production ready, you can implement pretty much same using the original SDK of the underline services. [1] https://temporal.io/ https://temporal.io/

revskill 4y ago
This is complicated with too many terminologies :(
verdverm 4y ago
Their pricing model is much preferred: https://temporal.io/cloud https://temporal.io/cloud i.e. pay for what resources you use instead of how many users you have. This is how we pay for AWS/GCP/Azure. I think a lot of dev SaaS could / should go this way.
- vpol 4y ago
  And if you don't store much inside the workflows themselves - it's quite cheap even if you have hundreds of thousands invocations.
  - verdverm 4y ago
    1M invocations looks like $25, which is really cheap
    - vpol 4y ago
      I meant daily, but it's still cheap.
      - verdverm 4y ago
        I was saying 1,000,000 requests, which is the same for any time period
- johtso 4y ago
  Unfortunately there's currently a steep mandatory support charge of $200 a month, which makes it unviable for smaller operations. I think they're planning to offer the service without the support aspect, which would be fantastic and I'd be first in line for..
vpol 4y ago
Not sure why everyone says it's too complex, maybe people get scared by the word idempotence.