~/talk

Using F# on Azure Functions in Production

Talkat Build Stuff 2017 · 2017-11-15..11-19· [serverless, dotnet]
links:none on file
slides:none on file

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

  1. 0:00Start
  2. 1:53THE GOAL IS TO GET CODE RUNNING IN PRODUCTION
  3. 17:20WHAT PROBLEMS DOES F# SOLVE?
  4. 19:36F# MAKE (FAKE) AS YOUR BUILD SYSTEM
  5. 20:43a type provider is an adapter component that reads schematized data and services and transforms them into types in the target programming language.
  6. 29:09HOW DID THE TEAM HANDLE F#?
  7. 32:55THE SILVER BULLET FALLACY
  8. 35:07Runtime running on Azure App Service Runtime can run locally
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.