> It just flat out won’t. Instead you’ll spend most of your time figuring out how to mate these functions with other services from that cloud provider.
If this happens it means the workload wasn't built correctly to start using 12FA/SOLID principals.
> The perceived value fallacy
Unsure of the point being made here. Serverless is a consumption based model - entirely opex in all the best ways.
> the promise of it [serverless] reducing the only code you write to business logic remains sadly unfulfilled.
While true, it doesn't paint the entire picture either (see the first point above). Most serverless becomes boilerplate at some point within an organization. In mature orgs with mature serverless deployments this is built into the CICD pipeline. This doesn't even require a large org with a dedicated platform team: a small team can do this easily but it does take time, some experience, and some good planning. Yes, the providers oversell the capabilities but they're not a complete lie.
> Folks don’t like to spend an order of magnitude more to monitor a system than the system itself costs to run.
I think this sums it up.
The big problem is that if the system is part of my core competency then I care deeply about it, and I'm not going to outsource anything that could get in my way.
If I'm willing to outsource something, I generally don't care that deeply about it. So, you're attempting to ask me for money for something that I don't care about--there's an upper limit to that.
The WordPress thing is a good example. I want someone I can yell at if the main website goes down, sure, but, if that doesn't affect my customers, there is no point in me paying $100/month to monitor it. Outsource to somebody and hit customer service when it goes down.
Question: isn't all the bureaucracy part of the business? I mean, in the real world you cannot ignore authorization, and all the friction in processes either. Isn't it naive to assume software is able to fully model around that? -- anything trying to do so is bound to fail (in that aspect), and is a priori just a lock-in?
If this happens it means the workload wasn't built correctly to start using 12FA/SOLID principals.
> The perceived value fallacy
Unsure of the point being made here. Serverless is a consumption based model - entirely opex in all the best ways.
> the promise of it [serverless] reducing the only code you write to business logic remains sadly unfulfilled.
While true, it doesn't paint the entire picture either (see the first point above). Most serverless becomes boilerplate at some point within an organization. In mature orgs with mature serverless deployments this is built into the CICD pipeline. This doesn't even require a large org with a dedicated platform team: a small team can do this easily but it does take time, some experience, and some good planning. Yes, the providers oversell the capabilities but they're not a complete lie.