Conversation

Replying to and
There's really not much difference -- you get an objectively worse network on AWS by most standards. The flexibility benefit of AWS doesn't even apply here because it will just bankrupt you if you use it. It's entirely a tactic to keep data within AWS, with absurd end results.
3
7
AWS looks a lot different as a developer working for a VC funded company compared to paying for it as an individual or small business. It's more than just highly anti-competitive and expensive. The pricing is a huge liability and most developers aren't experts on AWS pricing.
1
1
I think perspectives will be a lot different for someone that's paying for it themselves or as part of a small business. I won't touch a service where someone could either force me to take down my services or bankrupt me with $10/hour DDoS attacks. Simply not a serious option.
1
I'd happily pay more money to have the peace of mind from transparent and predictable pricing without metered traffic. It doesn't imply needing to manage bare metal hardware or individual VPS instances / dedicated servers. Here's a more 1:1 comparison:
Quote Tweet
Replying to @FiloSottile and @iangcarroll
ovhcloud.com/en-ie/public-c is an apples to apples comparison with baseline AWS functionality without metered traffic for instance bandwidth. Comparison between abstracted cloud services and managing your own servers isn't necessary. Can have cheap unmetered bandwidth either way.
2
1