Creating resources Azure vs AWS<\/h2>\n\n\n\n
Without even getting into writing any code yet we are greeted by the first difference: AWS allows to either create standalone functions or to provision Lambda Apps that are basically CloudFormation templates for a function and all related resources such as CodeCommit repo, S3 Bucket and project pipeline for CICD. Azure on the other hand always prompts to structure functions by sitting them inside a Function App. The reason for doing that is, however, slightly different: Function App is a collection of functions that share the same App Service Plan.<\/p>\n\n\n\n
Serverless Invocation<\/h2>\n\n\n\n
AWS does not assume any triggers and we’d need to add one ourselves. Adding an API Gateway as a trigger is totally possible and allows for HTTPS setup if need be. But because trigger is external to the function – we need to pay closer attention to data contract: API reference is helpful but the default API gateway response of 500 makes it hard to troubleshoot.<\/p>\n\n\n\n
Portal editor functionality<\/h2>\n\n\n\n
Another obvious difference between the platforms is built-in code editor experience. In AWS it is only an option for interpreted language runtimes (such as Node.js, Python and Ruby):<\/p>\n\n\n\n
![\"finding](\"https:\/\/blog.wiseowls.co.nz\/wp-content\/uploads\/2021\/04\/image-3.png\")
<\/figure>\n<\/div>\n\n\n\n![\"if](\"https:\/\/blog.wiseowls.co.nz\/wp-content\/uploads\/2021\/04\/image-2.png\")
<\/figure>\n<\/div>\n<\/div>\n\n\n\nAzure has its own set of supported runtimes. And of course, things like .NET and PowerShell get full support. There’s however one gotcha to keep in mind: Linux hosting plans get limited feature set<\/a>:<\/p>\n\n\n\n AWS supports .NET Core 2.1 and 3.1 and conveniently provides selection controls, while Azure by default only allows for version 3.1 for newly created function apps:<\/p>\n\n\n\n At first look such omission is very surprising as one would expect more support from Microsoft. This however is explained in the documentation<\/a>: .NET version is tied to Functions Runtime version and there is a way to downgrade<\/a> all the way down to v1.x (which runs on .NET 4.7!):<\/p>\n\n\n\n![\"rich](\"https:\/\/blog.wiseowls.co.nz\/wp-content\/uploads\/2021\/04\/image-5.png\")
<\/figure>\n<\/div>\n\n\n\n![\"even](\"https:\/\/blog.wiseowls.co.nz\/wp-content\/uploads\/2021\/04\/image-4.png\")
<\/figure>\n<\/div>\n<\/div>\n\n\n\n.NET version support<\/h2>\n\n\n\n
![\"AWS](\"https:\/\/blog.wiseowls.co.nz\/wp-content\/uploads\/2021\/04\/image-6.png\")
<\/figure>\n<\/div>\n\n\n\n![\"Azure](\"https:\/\/blog.wiseowls.co.nz\/wp-content\/uploads\/2021\/04\/image-7.png\")
<\/figure>\n<\/div>\n<\/div>\n\n\n\n![\"it](\"https:\/\/blog.wiseowls.co.nz\/wp-content\/uploads\/2021\/04\/image-8.png\")
<\/figure>\n\n\n\nOverall<\/h2>\n\n\n\n
Aspect<\/th> AWS<\/th> Azure<\/th><\/tr><\/thead> Language support<\/td> .NET Core 2.1, .NET Core 3.1, Go, Java, Node.Js, Python, Ruby, PowerShell Core<\/td> .NET Core 3.1, .NET Core 2.2, .NET 4.7, Node.Js, Python, Java, PowerShell Core<\/td><\/tr> OS<\/td> Linux<\/a><\/td> Windows or Linux (depending on runtime and plan type<\/a>)<\/td><\/tr> Triggers<\/td> API Gateway, ELB, heaps more<\/td> Built-in HTTP\/Timer, heaps more <\/td><\/tr> Hierarchy<\/td> Function or Function app<\/td> Function App<\/td><\/tr> Portal code editor support <\/td> Node.JS, Ruby, Python<\/td> Node.js, .NET, PowerShell Core,<\/td><\/tr><\/tbody><\/table><\/figure>\n","protected":false},"excerpt":{"rendered":"