logic is still written by the application developer, but, unlike traditional architectures, it’s run in stateless compute containers that are event-triggered, ephemeral (may only last for one invocation), and fully managed by a third party. One way to think of this is “Functions as a Service” or "FaaS". https://martinfowler.com/articles/serverless.html
+, • ,!#,!ACU • ")+$ • OS '!$,&*, Consumption Plan on Windows App Service Plan on Linux https://docs.microsoft.com/en-us/azure/virtual-machines/windows/acu
E#$$*2 6#(+# 20'#-*.)6 530'2/0#)' 3'3'6530''04*%' 31 3'3'BA BMRWQC ; >/&DPO8V 9@:ID9 • 9"'0/PO8VMW7LNQ;?6=J ECGHPO8VMW7LNQ Storage Queue ServiceBus Queue Kafka RabbitMQ HPA KEDA 1->N or N->1 0->1 or 1->0 … K E D A
Functions F1 F2 F3 F4 Orchestrator Function // calls functions in sequence public static async Task<object> Run(DurableOrchestrationContext ctx) { try { var x = await ctx.CallFunctionAsync("F1"); var y = await ctx.CallFunctionAsync("F2", x); var z = await ctx.CallFunctionAsync("F3", y); return await ctx.CallFunctionAsync("F4", z); } catch (Exception)
• Azure WebJobs SDK - the "core" of the Azure Functions runtime and many bindings • Azure WebJobs SDK extensions - the repositories of many bindings • Azure Functions Core Tools - the command line tool for Azure Functions • Azure Functions NodeJS Worker - support for running JavaScript functions • Azure Functions Java Worker - support for running Java functions • Azure Functions Python Worker - support for running Python functions • Azure Functions UX - the UX for the Functions development portal • Azure Functions templates - the templates which show up in the Azure Functions portal, Visual Studio, Visual Studio Code, etc • Azure Functions samples - repository for some samples on how the runtime works • Azure Functions VS Tooling - msbuild tasks for precompiled functions