> Cloud functions are really the easiest way to deploy code to the internet. I have to agree. Anyone who wants to see what the SoTA UX looks like should go try

> Cloud functions are really the easiest way to deploy code to the internet. I have to agree. Anyone who wants to see what the SoTA UX looks like should go try an Azure Function Quick Start guide (preferably v4/C#), use Github and just "let it happen". I watched my project manager set up the CI/CD pipeline by clicking 1 button, confirming GH org, and setting 3 DDLs. It's all done now. We push code and it goes live. Someone set up a custom domain with 2 extra DNS records and 3 clicks in the portal. No TLS certs to manage. It's all just handled. Anyone who is complaining about this stuff being hard or broken in 2023 is doing the intentional stick-in-bike-wheel meme. I found the experience to be so simple & robust that I insisted on it being the only experience we have moving forward. You can really build anything directly on top of an HTTP trigger function if you are clever enough and are willing/able to step outside of certain "norms". From an audit & compliance perspective, I don't see how the word "complexity" would be permitted to enter the lexicon. That is, unless we are talking about the complexity faced by your cloud vendor's compliance team. One massive advantage with serverless platforms is that - ostensibly - there is no sever. This eliminates entire libraries of audit items from your side of the fence.