Hacker News Reader

Their pricing model is much preferred: 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.

And if you don't store much inside the workflows themselves - it's quite cheap even if you have hundreds of thousands invocations.

1M invocations looks like $25, which is really cheap

I meant daily, but it's still cheap.

I was saying 1,000,000 requests, which is the same for any time period

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..

Not sure why everyone says it's too complex, maybe people get scared by the word idempotence.

This is complicated with too many terminologies :(