71–80 of 151 posts
I see that the prices on the M3 instances dropped a bit more than the prices on the M1 instances did, so they are encouraging us customers even more to move from the older HHD based instances to the newer, faster SSD based instances.
M1 is older hard drives and M3 is SSD? Didn't know that
This is huge. Startups everywhere are huge beneficiaries of this price war between Amazon and Google over the future of cloud computing.
Let's just hope they all stay in business so we don't end up with only one player in the market...who can then jack up prices at will.
Just out of curiosity, why would one choose AWS over Digital Ocean? Isn't DO considerably cheaper?
I find it bizarre that Amazon put so much effort into pushing the idea theat their killer feature is price. Plenty of people outflank them on price. What's best about Amazon it their tooling. They have hands-down better tooling than their competition.
I use gandi for my personal stuff (because I'm less bothered by the French government spying on me than the US one) and it's much cheaper than Amazon. But in terms of being able to easily mass-manage a complex environment? Not even close. DO? Don't make me laugh.
Earlier quoted context omitted.
You're locked into whatever rate your reservation is for. This is why you see rate fluctuations on the marketplace for the same instance type. It's also why a 3 year reservation may not make sense.
That makes sense, thanks for the clarification. Bummer, though. We just reserved a multi-AZ m3.large RDS instance last week. I wish AWS would take up Google's system of graduated price reductions over steady run duration.
Just out of curiosity, why would one choose AWS over Digital Ocean? Isn't DO considerably cheaper?
DO is great for hacking on personal projects. I prefer AWS for work stuff because firewall, security groups and networking are much easier to manage. I have not yet tried GCE but I may move some of my dev stuff over once they roll out the private git repos.
https://source.developers.google.com/p/PROJECT/r/default
You might have to turn it on in your developer console, not sure.
At the moment, pushing to its "master" branch tries to deploy to app engine, so that might not be what you're looking for.
You can clone it (and, in the future, your connected repos and other Google-hosted repos) with 'gcloud init PROJECT', and things should work nicely.
Earlier quoted context omitted.
That makes sense, thanks for the clarification. Bummer, though. We just reserved a multi-AZ m3.large RDS instance last week. I wish AWS would take up Google's system of graduated price reductions over steady run duration.
That's when you talk to an AWS account rep and twist their arm a bit.