Using F# on Azure Functions in Production
summary
A production changelog service is built and deployed: it integrates Octopus Deploy, TeamCity, Jira to fetch deployed versions and commit messages, parses merge commits and DB migration hashtag detection, and renders markdown/HTML changelogs. Implementation uses F# Type Providers (JSON, YAML, SQL) to get strong types, a small F# library for the diff logic, and is hosted as Azure Functions compiled DLLs. It runs in production for national student tests but Azure Functions tooling on macOS proves awkward.
AI-written summary · about
chapters (15)
- 0:00Introduction to devops
- 0:32Continuous delivery process
- 1:42Development to test
- 4:26Gated production deployment
- 6:25Automating change logs
- 8:20Integration strategy
- 10:05The role of F#
- 15:00F# and C# interoperability
- 20:08Serverless architecture
- 28:37Implementing the logic
- 37:26API interaction and parsing
- 41:47Testing with Suave
- 45:23Deploying Azure Functions
- 50:46Advanced architecture
- 55:13Conclusion and Q&A
related talks
53mUsing F# on Azure Functions in Production
11mTotal Rewrite: A Story About F# and Azure Functions in Production
01h 06mGo Pro on .NET with F#
44mLife after business objects. Confessions of an OOP veteran
58mWhy you should use F#
13mF# Without Windows
01h 01mThe F# Path To Relaxation
39mIntroducing Azure Functions for serverless .NET