I just moved https://vlang.io from Google Cloud (my free credit expired) to an Amazon Lightsail VPS (any VPS will do), and my spending went from ~$70 to $3.5/month.
And the performance actually improved a bit.
A properly designed monolith on a dedicated server/VM can easily serve tens of thousands of users just fine and will be far easier to maintain than this mess (plus way cheaper as well).
The main advantage of those tools is when you have a number of distributed teams and you want to scale to millions of users. For nearly anything else, a far smaller setup is what you want.
They know, and try to educate.
The crazy thing is, even used inefficiently, the Cloud is still a very good value prop for a lot of businesses.
AWS creates work, and creates spend, much more than it needs to.
This is all by design.
I can only imagine how the Oracle cloud must go for victims^Wcustomers.
Systems engineering is hard, on-prem or in-cloud.
What is there to say? There are huge scale inefficiencies in maintaining a small datacenter.
At $dayjob we have a small DC (8 racks). We’re facing chiller, UPS, and core switching/cabling replacements all within the next two years.
We did the math, public Cloud is cheaper for us, especially since about 80% of our instances can be shut down outside business hours.
Agreed. I've spoken with a few companies that could save quite a bit of money by buying RIs with a few clicks. With a little bit of work they could save a lot more moving large parts of their workload to spot instances. Almost feels like they want to brag about the AWS bill size...
possibly because that's what most of the job postings are requiring?
Still, they all get a load balance configuration to grab the free TLS certs with auto renewal while keeping configuration simple.
While I would not recommend premature TLS termination for critical business data, it is sufficient for many applications.
Admins get their familiar AWS console to configure the apps and I can make sure these are bundled in a way to be deployed on many different systems.
If I wanted to, I could use AWS identity provider like cognito and have it all in one place.
I think the main argument for cloud provider is the utility and convenience they provide for small projects.
While I do not like the business practices of Amazon and would never like to work for them on AWS, I am also lazy and cannot say I that they didn't develop something very useful.
Generally companies don't really care if a solution is 70$ or 3,50$ a month. They do care about my wage much more. Unjustifiable!
Sure, you could dump it all on a server somewhere without using any external micro services. But in my experience these project are much more likely to start to randomly haunt you from the past. And worse, I so actually have to maintain the servers.
And the price difference for inefficiently used services is mostly between 5$ and 15$. But these extra 10$ a month can easily be set off for reduced development or administration time.
If after ~40 years the service is still active, I would freely admit to that mistake.
Granted, this isn't applicable for application that do actually need to be scaled. But the time to launch for standard solutions that nudge a few bits here and there can be reduced quite a bit thanks to infrastructure like this. And it may be in use anyway since all the Google Home/Alexa IOT stuff.
There's certainly a huge range of pricing for the exact same services (sometimes worse services cough OVH dedi servers cough)