Using F# on Azure Functions in Production
summary
Builds an automated changelog service in F# that calls Octopus Deploy, TeamCity and JIRA APIs, parses merge commits and DB migration tags, and emails a generated changelog so customers can approve deployments. Uses F# JSON and SQL type providers for compile‑time safety, precompiled Azure Functions deployed as lightweight DLLs, and the actual Azure Functions runtime to run and debug locally. Service reduces manual QA steps and enables feature‑driven releases (several deploys/week, 20 minutes from change to production), with a noted friction: Azure Functions v1 F# dependency version mismatch.
AI-written summary · about
chapters (8)
- 0:00Start
- 1:53THE GOAL IS TO GET CODE RUNNING IN PRODUCTION
- 17:20WHAT PROBLEMS DOES F# SOLVE?
- 19:36F# MAKE (FAKE) AS YOUR BUILD SYSTEM
- 20:43a type provider is an adapter component that reads schematized data and services and transforms them into types in the target programming language.
- 29:09HOW DID THE TEAM HANDLE F#?
- 32:55THE SILVER BULLET FALLACY
- 35:07Runtime running on Azure App Service Runtime can run locally
related talks
58mUsing F# on Azure Functions in Production
01h 02mScaling Serverless F# with Azure Functions
01h 03mGrowing Serverless code with Azure Functions and F#
11mTotal Rewrite: A Story About F# and Azure Functions in Production
41mAutomating DevOps Releases using .NET and Azure Durable Functions
59mServerless Compute with Azure Functions
42mServer-less compute with .NET based Azure Functions
25mBuilding AI-Powered Applications with Azure Serverless Functions and C# .NET
