Functional Programming for APIs

on YouTube ↗26m

" summary

Argues that converting API endpoints into pipelines of pure functions improves testability and parallelism, but admits enterprise apps cannot be fully functional. Demonstrates using F#-style result types or practical C#/.NET business exceptions to unify validation errors and produce consistent HTTP error payloads via a global handler. Recommends micro types instead of raw primitives and prefers separate validated models over widespread optionals, notes the trade-off of more models for clearer, safer function signatures.

AI-written summary · about

" chapters (9)

1. 0:00Intro
2. 0:17About Revolut
3. 1:28What is this talk about?
4. 3:42What is «pure function?
5. 9:08Functional Cit: Handling failures, input errors
6. 13:02What's the advantages?
7. 17:30What's the trade-off?
8. 23:09Ideas to consider
9. 24:03Roman Nevolin

" related talks

• 56mFunctional Programming on .NET - The Best of Both WorldsIsaac Abraham · NDC Oslo 2024
• 28mHTTP through Functional ProgrammingAndrew Cherry · LambdaConf 2015
• 58mFunctional Programming with C#Simon Painter · NDC Porto 2022
• 01h 03mFunctional Programming with C#Simon Painter · NDC Oslo 2020
• 59mPipeline-oriented programmingScott Wlaschin · DotNext 2021 Moscow
• 01h 01mThe Functional ToolkitScott Wlaschin · NDC Oslo 2019
• 01h 06mThe Functional Programmer's ToolkitScott Wlaschin · NDC London 2019
• 01h 00mFunctional-first programming with F#Tomas Petricek · NDC Porto 2019