So the issue here is not really shared vs dedicated instances. The issue here is that a particular cloud provider (namely AWS) has set up an opaque fee structure.
So the issue here is not really shared vs dedicated instances. The issue here is that a particular cloud provider (namely AWS) has set up an opaque fee structure.
Who, in their right mind, goes for a bare metal to AWS, when there are so many decent and time-tested options out there?
I'd argue that startups should have a good reason for not using AWS. The costs for their basic services is not that much compared to the cost of development.
What I started doing is just running my own "cloud" out of my house for personal projects. I have all of the things I need. There's some overhead in terms of maintenance and up-front setup cost in terms of time and equipment, but after that it's pretty smooth sailing.
If it's literally called a dedicated server, why would you suspect otherwise?
Source: I worked in the core EC2 dataplane for a couple years. PEs and leadership there would not be happy with misleading customers. We constantly thought of the customer experience there.
It didn’t mean ”I suspect that what they are getting from Amazon isn’t a dedicated server”.
Rather it meant ”I suspect that they’re getting a dedicated server from somewhere else that isn’t Amazon”.
The original comment was talking about a dedicated machine for personal projects with a fixed cost of $40/month.