[nailer]

Reconsider it. Unless your enterprisey company is building a platform itself, you don't care about VMs, containers, or MicroVMs.

Build serverless workloads and run them on whatever compute is available.

[donmcronald]

How do you build serverless workloads that are portable between compute providers?

[k__]

You don't.

The the money you spend for being provider independent is the very money you save by going serverless.

Leaves the question: Is the risk worth the money saved?

[GordonS]

Azure's Function App engine is OSS, so you could go with Azure's FaaS, but retain the option to self-host on VMs or servers anywhere.

[alexellisuk]

OpenFaaS (around 2.5 years since launch) with 200 contributors, 17k stars and around 40 end-user companies in production. www.openfaas.com

[donmcronald]

Thanks for this! It looks very cool.

[kauboy]

How about Google cloud run?

[solatic]

Knative, but it's still immature, like most serverless frameworks.

[nailer]

Most serverless frameworks give you some degree of portability across the majopr providers. I work on architect (which is currently AWS only) which is going to add Azure support pretty soon.