News for hackers. Stuff that matters.
Re:Azure Functions – Significant Improvements in HTTP Trigge... by joncrane on Friday March 09, 2018 @02:41PM (#16554324)
Is this the Azure equivalent of AWS Lambda?

What factors other than some specific affinity to Microsoft makes a company choose Azure over AWS?

Re:Azure Functions – Significant Improvements in HTTP Trigge... by paunchy on Friday March 09, 2018 @09:16PM (#16556723)
We have no Microsoft affinity but have moved our large SaaS application from AWS to Azure. Our tech stack is 80% linux / OSS and 20% .NET. And we're deprecating the MSFT portion as quickly as possible.

For us, Azure was a big win for security compliance and data sovereignty. Those factors triggered the switch.

After the switch, we came to realize that Azure is much stronger in support and in the ability to interface with the Azure product teams to help guide the direction of the platform.

I've seen some recent reports that Azure is growing twice as fast as AWS so I wouldn't count them out by any means.

Re:Azure Functions – Significant Improvements in HTTP Trigge... by maltalex on Friday March 09, 2018 @03:24PM (#16554674)
> Is this the Azure equivalent of AWS Lambda?

Yes.

> What factors other than some specific affinity to Microsoft makes a company choose Azure over AWS?

Azure has a decent offering even if you don't have any "specific affinity to Microsoft". You can use Azure to develop products that don't use any Microsoft technologies. Although from my own experience, Azure tends to be a bit rough around the edges especially when used with non-Microsoft tools and languages.

See marketing page: https://azure.microsoft.com/en-us/overview/azure-vs-aws/

Re:Azure Functions – Significant Improvements in HTTP Trigge... by rraval on Friday March 09, 2018 @04:22PM (#16555162)
> What factors other than some specific affinity to Microsoft makes a company choose Azure over AWS?

We have data residency requirements to keep things in Canada. This actually forced us to migrate off AWS, first to IBM, then eventually to Azure.

Re:Azure Functions – Significant Improvements in HTTP Trigge... by Thaxll on Friday March 09, 2018 @04:26PM (#16555199)
Re:Azure Functions – Significant Improvements in HTTP Trigge... by rraval on Friday March 09, 2018 @05:02PM (#16555414)
Cool, I didn't realize that. Thanks for the correction.

I should mention that this was back in September 2014, where IBM was the only one offering anything in Canada (hence the migration).

Once we'd done all the work to decouple from AWS, it was fairly straightforward when Azure came knocking and offered us a ton of compute credits from their startup program. IBM had also rebooted a couple of critical VMs with no prior warning which left us wanting a cloud provider that took its tenants seriously. This was in ~May 2016 and we hadn't heard anything about a Canadian AWS datacentre, which apparently launched in Dec 2016.

We still use SES to this day because we haven't found a good alternative, so it's not like we hate AWS or anything. Just offering a (dated) perspective on why someone might choose Azure.

Re:Azure Functions – Significant Improvements in HTTP Trigge... by jeffhollan on Friday March 09, 2018 @04:30PM (#16555223)
In the serverless space - a few deciding factors we see people weigh (disclosure: Functions PM in Azure)- * Dev tooling. VS Code and Visual Studio 1st class tooling, including local debugging/breakpoints * Pricing. No API Gateway layer so these types of high load scenarios become significantly less expensive * Platform. Azure serverless is much more than just functions. Also serverless workflows (Logic Apps) and Events (Event Grid). Also enable multiple hosting models (serverless, dedicated, on-premises)
Re:Azure Functions – Significant Improvements in HTTP Trigge... by CyanLite2 on Saturday March 10, 2018 @12:32AM (#16557262)
Cheaper costs, CosmosDB, better AI integration, compliance, enterprise integration, more regions, etc... etc...

CosmosDB was the difference for us.

Re:Azure Functions – Significant Improvements in HTTP Trigge... by evfanknitram on Friday March 09, 2018 @02:42PM (#16554337)
Yes it is.

What do you mean by Microsoft-specific stuff? I run a bunch of stuff there. When I started using these things their PaaS offerings were much more mature than the AWS counterpart (since they focused more on IaaS).

Re:Azure Functions – Significant Improvements in HTTP Trigge... by viggity on Friday March 09, 2018 @11:32PM (#16557104)
We run all PaaS except for two very special case VMs. It is an effin' delight not having to worry about security, maintenance, updates. I just deploy my code (app services) and query my data (azure table storage, azure sql). Shit just works. Every time I need to deal with the VMs I cringe.
Re:Azure Functions – Significant Improvements in HTTP Trigge... by philliphaydon on Saturday March 10, 2018 @11:27AM (#16559053)
Examples?
Re:Azure Functions – Significant Improvements in HTTP Trigge... by dewiz on Friday March 09, 2018 @02:48PM (#16554394)
yes people use Azure to host all sort of services, OSes, programming languages etc. Companies run Microsoft stuff on Google cloud and AWS too, surprising eh?
Re:Azure Functions – Significant Improvements in HTTP Trigge... by Qworg on Friday March 09, 2018 @04:04PM (#16555022)
Deep support on the corporate and technical levels.
Re:Azure Functions – Significant Improvements in HTTP Trigge... by gaius on Saturday March 10, 2018 @03:24AM (#16557686)
What factors other than some specific affinity to Microsoft makes a company choose Azure over AWS?

More locations, tho' every major cloud is opening more all the time. A much better hybrid story, tho' this may change once (if) AWS get their alliance with VMware working properly. Better layered applications (X-as-a-service) but that might be a matter of taste - AWS is more about giving you building blocks to build your things, Azure has the blocks but is better at giving you integrated "things" out of the box (e.g. IaaS vs PaaS). Per-second billing, generally better budget control.

I've a bit of experience with both Azure and AWS. There's nothing I could build in one that I couldn't build in the other, tho' depending on what that is, it might be more effort in one of them. For my own personal stuff, I use Azure, it's more fun :-)