I find the actual deployment with cloudfunctions easy as you say. The complexity is the orchestration, the architecture, the hard vendor limitations, having to

I find the actual deployment with cloudfunctions easy as you say. The complexity is the orchestration, the architecture, the hard vendor limitations, having to deal with being a distributed system. Having a FAAS service makes the deployment easy but development wise a traditional monolith deployed on static servers can be far simpler to deal with. I use FAAS (Lambda's /cloudflare functions) a lot for pet projects as it costs me fractions of a cent to host. The architecture is quite complex being distributed, dealing with restrictions, eventual concurrency etc etc. I find it enjoyable making things work in these systems basically for free but if these projects where a business with paying customers, alot of the stuff I'd drop from FAAS and deploy on static VPS servers as architecture is so much easier meaning I'm much more productive. With paying customers I can take the additional cost of a few VPS's or dedicated hosts such as Hetzner. The FAAS wouldn't outweigh the productivity gains.