TrueTeller

(Pulumi providers dev here)

This has been the case in the past but we are investing in our provider ecosystem. We built several first-party native providers that aren't based on TF: Kubernetes, Azure, Google. Now, we also encourage third-parties to build their integrations.

Here is a boilerplate repo of a resource-based provider: https://github.com/mikhailshilkov/pulumi-provider-boilerplat...

Here is a provider that is driven by an Open API spec: https://github.com/mikhailshilkov/pulumi-provider-boilerplat...

For simple use-cases, you've always been able to build Dynamic Providers in TypeScript or Python: https://www.pulumi.com/blog/dynamic-providers/

Please reach out if you want to build a provider and we'll definitely help you out.

Hi, the author here. It's a good point and a valid concern, but I did an explicit choice here: I didn't want to make the article longer. I have a prequel post which describes my thinking of why durable functions make sense, including a primer for the event-driven approach: https://hackernoon.com/making-sense-of-azure-durable-functio...

"Analysis" is not that hackernews-worthy :P

IMO, every greenfield app that can benefit from "just focus on your business code" model.

P.S. I'm the author of OP, thanks for reading!

That's all plausible except the price issue. Say, you keep 10 containers alive, so you make 10x 100ms calls every 5 minutes. That's gonna be $0.20 per month. 20 cents.

Yes, one could prewarm N instances by sending N parallel requests every 5 minutes. You have to know N though :)

For most apps, scale-out cold start won't be too much of a deal breaker: longer instance lifetime + shorter start will do the trick. And wait for the next wave of optimizations from vendors, I'm sure there's more to come.

P.S. I'm the author of OP, thanks for reading!

There are some, e.g. https://github.com/jeremydaly/lambda-warmer and my post https://mikhail.io/2018/08/aws-lambda-warmer-as-pulumi-compo...

1. Most applications don't need the warm-up since they aren't too critical to cold starts.

2. Cloud vendors are working and succeeding to make cold starts faster, and AWS is at the forefront.

3. Pre-warming done right is extremely cheap, you won't pay anything meaningful, just several cents per month.

P.S. I'm the author of OP.