Years ago I told one of my coworkers that I brought in my bike to the repair shop to replace the tire for €15. "€15? You can just do that yourself?" Sure, but I'd spend 30 minutes mucking about and and getting my hands dirty. It's not like I got a stash of money to burn, but I'd rather just pay the €15.
We had more troubles with work with "the cloud".
Setting it up was just pressing publish in VS + git and 1 time the domain+site ( 5 minutes in total ). So I spend less time on it.
Everyone seems to forget that every deployment needs to be configured somewhere. If not by you, someone else.
The server is windows server with IIS. Nothing special, you can get it for the price of an 1 Shared App Service in Azure ( 10 € / m = 1 Windows Server) vs 8€ / month ( 1 Shared App Service).
I didn't had to do maintenance in the last year. But I did create a custom statuspage. But it's used mostly to deliver updates of clients when I deploy ( it creates a RSS entry when I deploy, which clients can receive).
Clients are notified 100% of the time with updates from the developer as soon as it happens, if they want it :)
I suppose with your 20 years of experience ( Github exists since 2008 as a reference), you can give me some actual examples that the cloud improves on workload?
Eg. I have a small member management saas that I haven't touched in the 6 years that it's running. I just realized that it's probably hosted on my test server ( my first VPS) and if it wasn't used, I wouldn't have been able to send the yearly invoice :)
The dogma is in thinking that the cloud makes everything simpler. It isn't. It makes difficult things more simple, but in a lot of cases, you don't need them in the first place.
> The dogma is in thinking that the cloud makes everything simpler.
I never said anything of the sort. Everything comes with trade-offs. I host my product on two Alpine Linux VPSs. But I also spent time setting all of that up and need to spend time maintaining it. For personal projects, cloud tools like FastMail tend to be the better choice in most cases.
I was talking about client projects. Hosting email isn't a client project and is something I wouldn't selfhost either.
When I mean creating projects in the cloud, I'm talking about using the big 3 Google, Microsoft and Amazon cloud. I even explicitly mentioned azure...
Netlify is build on top of AWS and for them, it's useful for actual scaling on the "edge". But most sites on netlify don't need their edge capabilities.
And cloudflare is one self hosting it on more edge locations ( i think they could even join the big 3 soon)
And still, some customers had issues 21 days ago with netlify DNS. So those clients spend time on that too and didn't knew what was happening at first
https://news.ycombinator.com/item?id=26581027
Additionally, here are some edge cases you can run into for DNS:
https://answers.netlify.com/t/support-guide-dns-quick-start-...
But i guess those issues don't count as "maintenance/work" :)