Understanding Azure Functions for containers
As we discussed in the introductory chapter of this book, containers are like packages containing everything it needs to run the solution. All we need is a container runtime. Azure Functions can provide that!
Normally, when you look at the capabilities of Azure Functions, you might quickly determine that the sky is the limit. But, let’s picture the following scenario. You build your solution using Azure Functions, and you have about 20–30 Azure functions. Pretty awesome! But, you have that one runtime or that one specific task that just cannot run on Azure Functions. That is when containers come in.
Before we start doing some container magic, let’s first take a look at Azure Functions in general. As we mentioned in the introduction, Azure Functions is serverless and only consumes compute when it is executed. So, how do you run it?
Azure Functions comes with triggers and bindings. Basically, triggers are what...
