Help! We’re inheriting a large F# application
summary
A large F# service at NRK handles favorites and resume playback for logged‑in users, runs on the Orleans actor framework, and serves roughly 50–80 million requests/day with peaks near 1,700–2,100 req/s. The team inherits the code, ships fixes and features without frequent outages, reorganizes domain types and signposts cross-file invariants, and wrestles with brittle tests, monitoring gaps, and awkward Azure SDK interop while gradually owning the core domain and deployments.
AI-written summary · about
chapters (17)
- 0:00Intro
- 2:46Once upon a time...
- 6:46You're all an island
- 8:34People use NRK TV & Radio quite a bit
- 13:30Keep important stuff in view
- 14:34Functional domain modeling is nice
- 17:36Functional view is also limited
- 18:57Use signposting to guide travellers
- 19:37Comments and tests can be signs
- 22:41Documentation comments as signs
- 24:32The F# programmers pathfinder
- 26:40Consider drawing maps
- 27:49Mapping with documentation
- 30:12Let the mob be your map
- 34:15Most .NET stuff is quite easy to use
- 35:07Plenty of goodies in the F# community
- 40:14Functionality we love to own
related talks
46mEvolving architecture with DDD and hypermedia -
01h 02mFishbowl @ Functional Conf
54mCtrl-Alt-Del: learning to love legacy code
51mExperiences from large project maintenance at the Norwegian tax authority
45mTaming the FinTech Beast
01h 01mArchitecting for rapid, frequent, reliable delivery of software.
38mIt's Simple…
31mScaleable Service Frameworks