Cloud Wars - Amazon v. Rackspace v. Microsoft v. Google
-
Went from Amazon to Azure as it is a much simpler product. Been very content with the outcome.
Same here
To alcohol! The cause of, and solution to, all of life's problems - Homer Simpson ---- Our heads are round so our thoughts can change direction - Francis Picabia
-
<Edit>Brainfreeze removed, my apologies</edit>
Wrong is evil and must be defeated. - Jeff Ello
-
I've only really used Azure. I used to colo some servers with Rackspace, but never used their cloud stuff. So far, except for some billing discrepancies Azure has worked pretty well. But, I cannot stress this enough, the customer service at Rackspace is totally freaking awesome. If you can afford, those guys are nothing short of a blast to talk to.
Jeremy Falcon
^ *Jeremy Falcon, Rackspace Customer Service
-
Just wanted to see what the lounge consensus is for cloud migration. Winner / choice and why? At a previous job, we hosted on Amazon, and I remember they had some proprietary scheme for db backups where you couldn't get at your backup except to restore it on their servers/systems. Anybody know if this is still a constraint?
-
<Edit>Brainfreeze removed, my apologies</edit>
Wrong is evil and must be defeated. - Jeff Ello
Uh. AWS is Amazon?
-
Uh. AWS is Amazon?
Nope. :sigh: :-O
Wrong is evil and must be defeated. - Jeff Ello
-
Just wanted to see what the lounge consensus is for cloud migration. Winner / choice and why? At a previous job, we hosted on Amazon, and I remember they had some proprietary scheme for db backups where you couldn't get at your backup except to restore it on their servers/systems. Anybody know if this is still a constraint?
Having deployed several .Net applications to Azure and AWS (standard type of web app with asp.net, sql server, some background services, some queuing, blob storage, caching, CDN) I'd say that if you're in the .Net world then you'll get a lot more productivity out of Azure (unsurprisingly).
-
I recently did an AWS certification. I hadn't done much Cloud before and I was really impressed by the platform. It's really amazing and as they have over 90% of the market and massive ongoing investment, it's a great choice. I'm not aware of any backup restriction with any of their database services. What Database are you using? If none of the AWS DB services suit, you can always run your own DB instances on EC2 and backup to S3.
Tired of over zealous filters claiming your good email is spam? Then try Email Saviour, it's toasted hosted. (Thanks Don Draper)
Have looked at AWS in attempting to move a client to the cloud. I find their pricing outrageous, their support abysmal, and their attitude towards small businesses that have to be concerned about the cost of the service one of "Don't call us, we won't call you." It really seems like they do not want our business, which is a shame as I have several other clients I would like to move to the Cloud. The documentation seems to be deliberately misleading and confusing (Think the language in your insurance policy.) Can you tell I am frustrated? On the plus side, the VB6/ADO.net applications I have developed run well on the Windows 2016 virtual server and the database performs well on the MS SQLServer2016. (I do attribute this more to Microsoft than Amazon, however.)
A giraffe is a horse designed by a committee....
-
Nope. :sigh: :-O
Wrong is evil and must be defeated. - Jeff Ello
Amazon Web Services
-
Just wanted to see what the lounge consensus is for cloud migration. Winner / choice and why? At a previous job, we hosted on Amazon, and I remember they had some proprietary scheme for db backups where you couldn't get at your backup except to restore it on their servers/systems. Anybody know if this is still a constraint?
I've used both Azure and AWS and find Azure to be easier and more friendly to use and use it for my side projects. That being said AWS has been around longer (it's interface still looks pretty much like it did back when it first came out). In the company I'm currently with we have a lot of constraints around data privacy and regulations to follow and have been using AWS as we found Azure didn't fully meet those needs yet (parts of AWS are off limits to us as well due to the same issues). I'd recommend Azure if you don't have an regulatory constraints as it's the easier product to use. If you do have constraints then you'll have to sit down with the lawyers and figure out which one will work best (probably AWS).
-
Just wanted to see what the lounge consensus is for cloud migration. Winner / choice and why? At a previous job, we hosted on Amazon, and I remember they had some proprietary scheme for db backups where you couldn't get at your backup except to restore it on their servers/systems. Anybody know if this is still a constraint?
I've used Azure, AWS, and Rackspace (VM hosting, Sites, Cloudfiles).... but all on different projects, so not really a good comparison. I will say Rackspace's customer service is by far the best. They even sent me a package as a 'Sorry' when it took them longer than normal to respond to a message (package contained a leather bag with embossed rackspace logo, a bluetooth speaker, a leather notebook with embossed logo, some pens, a shirt, a water bottle, and a few other things). But as for everything else, it was 3-4 years ago so I'm not sure if my experience is even relevant anymore. VM hosting worked well. CDN worked well. Azure was nice and simple. Autoscaling worker roles worked most the time and the uptime on our stuff never had any issues. And I have the luxury of working with a guy that worked on both Azure AD and Azure table storage at Microsoft, so we have thoroughly abused the table storage system. VM hosting worked well, though felt expensive. Table storage was dirt cheap (which was why we abused the hell out of it to store several TB of CSV data). Wouldn't recommend using Azure Web Sites for anything complex, as we ran into a bunch of issues (though again this was a few years back, so may not be relevant). On AWS we used Lambda (to mock up some APIs and serve a static Angular front end out of an S3 bucket), DynamoDB, and EC2 (for stream processing) for a quick PoC, which seemed to work really well. But again, I work with several ex-Amazon employees who actually worked on ECS, Lambda, Dynamo, and Route53. Our current project right now is 100% container based microservices on ECS, which we haven't really had any issues once we got the ELBs and CLBs configured (persistent TCP connections can be a b*tch). Auto scaling wasn't working for us, but that was due more to the nature of our services rather than an issue with AWS.
Senior Software Engineer / Automotive Hacker