"Any sufficiently advanced technology is indistinguishable from magic." Azure Functions is quite an advanced technology. As a result, it's often treated as magic. But from an engineering perspective, treating technology as magic often backfires.

I've been building solutions based on Azure Functions since v2 has been released. I've used them the right way. I've used them the wrong way. I've integrated them with technologies that they weren't out-of-the-box ready to be integrated with. I did encounter challenges, and whenever I did, I used one of the best pieces of advice in software engineering - "always understand at least one layer of abstraction below the one you're working at". This approach allowed me to gain knowledge and understanding of Azure Functions.

In this talk, I want to share some of that knowledge and understanding with you. I want to show you the anatomy of Azure Functions triggers and bindings. It's the triggers and bindings that define the boundary between your business code and the runtime. They impact how your solution is scaling and how it handles parallel processing. This is why I believe it's valuable for you not only if you are looking to integrate Azure Functions with additional technologies, but whenever you are building function apps.