https://news.ycombinator.com/item?id=12270129
AWS and Azure overcharge on bandwidth about 10 to 20 times the prevailing rate. Something to keep in mind for high bandwidth applications.
The only explanation I can think of for this is that they probably want to compete on price with AWS, while keeping profits from their traditional customers high.
---
You're not paying for hardware. You're paying for hardware, expertise, services, and convenience.
On-prem or colocation may be a good choice. But limiting your comparison to raw computing power mischaracterizes the decision.
Plus, there's also a premium just for access to the ecosystem/APIs. You are often paying for the theoretical convenience of being able to spawn additional instances programmatically.
And you can use both at the same time (dynamically scale up through cloud, bare metal predictable workloads)
Turns out server admin is not my skillset, and it's caused problems, headaches and risks in the past.
I consider the additional cost going forwards in effect as our next hire and an important one. For small startups looking to save money DIY can be a good option, but moving onto the cloud at a later date can be a big burden.
Want to build a 1TB DDR4 RAM beast with 40 cores? Yeah, you can do that with dedicated.
But nobody uses AWS 'cause it's "cheapest". That's completely missing the point.
What reasons push people to pay upfront and to commit to a solution whose main benefit is elasticity?
There is likely some optimal schedule where you start w cloud, order DIY replacements, and migrate, and repeat as you scale. Labour-intensive though.
No? They don't? Maybe that's because you're comparing fundamentally different things that are only superficially similar to each other.
It was very disappointing to see the auto-scaling services for GCP and AWS basically require a $20/mo load balancer right off the bat. I have an app that is quietly puttering away on a single Digital Ocean droplet, but could at any moment, uh, make it big and I want to be ready. But I can't really stomach the $20 just to turn on auto-scaling somewhere.
There's kind of this uncanny valley of businesses who think their website/app-backend is kinda important, but keep asking about $5 or $20/month hosting when you've recommended ~$100/month for a load balanced redundant AWS setup. If you aren't prepared to pay for a load balancer, at least two ec2 instances, and a multi-region RDS instance - I don't really want to get your 2am Saturday morning phone calls asking why your site/app is down.
Advice: investigate your devops tool of choice (I like Ansible) and work out how to script the spin up of infrastructure at Digital Ocean - you'll need to invest some time to learn and get it working, but you should be able to set up a single command line script to provision additional droplets and add them behind an (automatically updated via Ansible/APIs) dns round robin set of "Floating IP" addresses (or Elastic IP addresses in AWS terminology) and use Heartbeat on each droplet to monitor the others and re-update the Floating IPs as needed. That's kind poorman's HA. For extra credit, you could work out how to automate provisioning of some HAProxy Droplets sitting in front of your app server droplets. Managing a shared database is left as an exercise to the reader who prefers not to pay for RDS ;-)
aws elb support http and https termination, and can even provide free SSL certs. Azure's is tcp/udp only.
And the new aws Application load balancers offer even more features.
So it depends on your use-case.
Then again, AWS is also pretty atrocious as well (just rear Glacier horror stories). But more people understand the pricing with AWS.
I find that Azure is about 1.5x the price of similar services from AWS. I've not looked at GCE.
But those are my experiences. YMMV
In Amazon's defense, their pricing is pretty clear and straightforward except for Glacier, which even they admit doesn't follow their pricing model for all the other services.
Google's is still the best though -- they automatically give you "bulk discounts" instead of having to buy them in advance like AWS, and their general philosophy is "your cheapest option should be to finish your workload as quickly as possible", as opposed to AWS, where you have to do some acrobatics to fit into their pricing models efficiently.
[1] https://azure.microsoft.com/en-us/pricing/details/sql-databa...
Another point is, Google's VMs are generic CPU/RAM combinations. You don't need "network optimized VMs" or "storage optimized VMs" - you simply get those things on any VM. This makes the "excess instance supply" market much more fluid and simplifies folks' lives.
Happy to discuss further!
(work at GCP)
Frankly, I'm beginning to think that things are swinging back to dedicated. I'm seeing ~$30 to ~$50 / month deals on a lot of dedicated servers (years old Xeon boxes), which have the main advantage of dedicated I/O. (No "neighbors" eating up the SSD or HDD IOPS).
https://www.nocix.net/dedicated/
https://www.kimsufi.com/uk/servers.xml
For a certain scale, aiming at dedicated is probably cheaper, especially when you consider how much faster a dedicated SSD box is than a shared VPS.
The main benefits of AWS (or Azure) are all of the other features they offer on their platform. But I don't think that they are low-cost anymore, especially in today's world with ~$42/month dedicated SSD Xeon servers.
You also get credits when buying VS/MSDN.
For non-production use only. There's a lot of fine print on the MSDN "free credit."
I currently make it build on my machine at home, but that't not very scalable or reliable.
I don't really want a full windows machine. I want a decent windows machine for doing builds that only runs for a few hours in total each month and is cheap.
Is there such a thing?
We love Azure, and we would like to use it for all our web projects, but it is hard to justify it with the current pricing.
Shoot me a message (email in profile) if you have questions. I do not get heavily involved in licensing discussions, but can try to answer more questions if you have them. If you want to build a SaaS on Azure, though, you are the customer Microsoft wants - take advantage of that.
