Reliable Client Server Data Transport for F# web applications
summary
A library called Fable.Remoting provides a native F# RPC layer that combines REST and gRPC ideas into a single, type-safe client/server model and claims no code generation is required because contracts are F# types and proxies are built at runtime. It runs with Giraffe/Saturn/ASP.NET Core, preserves decimals, DateTimeOffset, options, unions and recursive types, offers raw byte[] file upload/download and an optional MessagePack binary transport, generates interactive docs and error handlers, and the demo shows a working todo add/get cycle.
AI-written summary · about
chapters (33)
- 0:00Intro
- 0:20Agenda
- 0:53About me
- 1:22Context
- 2:15Problem
- 4:07Client server interactions
- 5:21Post request interactions
- 6:01Figma remoting
- 7:07Existing solutions
- 9:32What is Remoting
- 11:03How does it look like
- 13:06Implementation
- 14:18Fable Remoting
- 15:18Fable Remoting Frontend
- 16:44Combining Remoting with Web App
- 18:10Supported Types
- 21:48File Transport
- 25:07Message Pack
- 26:14Dependencies
- 27:49Injected Services
- 28:41Example
- 33:06ServiceConfig
- 33:58FromContext
- 36:00Proxy
- 36:59Logs
- 38:59Adding Functions
- 40:36Documentation
- 43:55Enhancements
- 45:27Add to do
- 46:10Error handler
- 48:27Getting started
- 48:57Thanks
- 51:19Questions
related talks
27mTake a rest from REST
26mThe hidden framework revolution: the comeback of RPC
53mIntroduction to T(ype)DD with F# and Reactive Web Apps with Fable.io
12mtRPC: Better than REST GraphQL?
56mHow To "Dot" Into Anything, Anywhere, Anytime (Facilitating Data-First Programming)
13mMaking typesafe APIs easy with tRPC
05mFull-stack & Typesafe React (+Native) Apps with tRPC.io
52mType-Driven Development with F#