Yeah, I mean my prior level was - spin up a single EC2 instance and do all the dirty stuff there, or just throw everything at vercel interfaces. In a short timespan I was able to learn how to spin up some kind of alien future technology servers. I don't need AWS Elite Certificate now to be able to navigate their bulky GUIs. I don't even need the GUIs or some hefty cli multiliners, just some very clean and declarative .yaml configs in the dark vasts of my vim, and it spins up. Next level stuff.
Would it save more if you did not choose microservices, but wrote a monolith (for purposes of deployment) neatly divided into modules (for purposes of architecture and splitting the work)?
I'm not assuming positive answers. But I know that current hardware is absurdly performant, and you can serve a surprising number of real users from a $60/mo instance, plus some database.
(Managing monoliths via k8s is a thing though, and it works reasonably well.)