Azure Function Anatomy

In this lesson, we’ll examine the components that are common to any Azure function type, regardless of the language and runtime configuration that the function is based on. It doesn’t matter whether our function is written in Java, Python, or C#. It will still run the code in the same type of process. The following diagram demonstrates the basic structure of any Azure function:

An Azure function runs in its own process. The process acts as a container for the executable code, whether it’s a compiled executable file, interpreted script, or a separate executable process. The process also contains a binding configuration that determines how the executable code is triggered. When a specific type of event occurs in a specific place that the function is configured to listen to via its binding configuration, the executable code of the function is triggered.

Azure function bindings configuration

Each Azure function has a function.json file that provides the configuration of a function trigger, inputs, and outputs. With compiled function types where such data is set in the code, this file is auto-generated when the ...