|
|
|
Only for a horse with no name
In Word you can only store 2 bytes. That is why I use Writer.
|
|
|
|
|
It felt good to be out of the rain.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
In the desert you can remember your name
In Word you can only store 2 bytes. That is why I use Writer.
|
|
|
|
|
Anyone here who has used both (either at the same time or at different times)? If so how did the experiences compare?
|
|
|
|
|
I've only used Azure from the standpoint of systems engineering type stuff. As a dev I've used AWS also, but of course that don't really mean much in this regards. Anyway, my opinion is that I think an EC2 instance looks a tiny bit "cleaner" if that makes sense when freshly going. Not by much and certainly not enough to chose one over the other, but figured I'd chime in with that.
That being said, as of right now, I know of more companies moving to AWS rather than Azure. FWIW
Jeremy Falcon
|
|
|
|
|
Thanks Jeremy. We use Azure at work but there are frequent down times, no warning, and recovery is not quick enough. Are there AWS equivalents for everything Azure offers?
|
|
|
|
|
|
Ah, thanks again. 
|
|
|
|
|
Also, if you want to play around with it. Amazon will give people like a free year with a low tier instance. They'll want a CC when signing up but won't charge it unless you host something like YT on it and kill their servers...
AWS Free Tier[^]
Jeremy Falcon
|
|
|
|
|
That would be quite handy - to get a feel for it. Thanks Jeremy.
|
|
|
|
|
You're totally welcome.
Jeremy Falcon
|
|
|
|
|
I've used AWS for a few years at Crate and Barrel and Azure here at my current job. The basic way I describe the differences between the two are that AWS can be a bit more of a low-level experience than Azure. It has a ton of functionality and you can do pretty much anything with either platform, but you will be doing a bit more work out of the box in AWS to get auto-scaling and other services working. I was able to set up Nginx as a reverse proxy and web servers in the backend pool and it worked really well. It was a mix of Linux and Windows. I used virtual machines and auto-scaling groups in AWS whereas in Azure, I did the same thing but with all managed services (App Gateway, Web Apps, Azure SQL). If you are working primarily in .NET, you'll find that the tight integration of all the microsoft products has great support. Linux is supported well too. I'd go with Azure if you are doing development in .NET. Both Azure and AWS seem to have roughly the same availability. I've had outages on both platforms, but they are infrequent.
|
|
|
|
|
Thank you. That was quite useful.
|
|
|
|
|
I've used both (albeit not touched AWS for several years) and found that Azure was much easier to get up and running.
|
|
|
|
|
Thank you, that seems to be the common opinion.
|
|
|
|
|
|
Thank you. I am not surprised that Azure is easier to setup compared to AWS, especially if you are hitting it from .NET. And I agree, years of Microsoft centric development can put you into a mindset where anything non-Microsoft looks difficult to navigate. It's a psychological block in my opinion than anything else.
|
|
|
|
|
I don't really have experience in either (although I've seen "some" Azure and it looks great).
However, what I've been hearing about Azure is that it's really been catching up to AWS in the past two years or so.
So if people choose AWS over Azure one or two years ago because it was so much more mature than Azure that might not be true anymore 
|
|
|
|
|
|
I worked with a Linux person that badmouthed Azure's Linux offering because it took several minutes to spin up a VM. He was working toward "servers as cattle not servers as pets" and wanted to be able to replace the prod environment quickly as soon as a problem was detected.
I actually faced a MSFT rep and showed her the difference between spinning up a CentOS machine on Azure [~2 minutes] vs. Digital Ocean (I think) [45 seconds].
That's from memory, but the difference was between one and three minutes. Timing is just for the machine to be available - I used the interface, using powershell may be faster.
(They never gave me the keys to AWS so that's all I had - don't know the AWS time.)
She didn't have a good response - but she was new and that was a year ago so YMMV.
Hope that's helpful,
-Chris C.
|
|
|
|
|
Useful info, thank you.
|
|
|
|
|
I ran across something about reserve instances, it sounds relevant, but to be honest I'm more of a dev than a devOp person these days (at this job; everything subject to change!).
Also, the 'better than per-second billing' in Azure where the round down to the nearest minute may be important if you're servers blip in and out of existance (345 seconds would be billed as just five minutes).
Full disclosure I do have an Azure personal preference because it is so easy to spin up and use sql server and .net.
HTH,
-Chris C.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
