Building Reactive Services using Functional Programming
summary
Company stack uses F# for most backend work and runs ~20,000 orders/day. Code demonstrates immutable events, async workflows with let! and Async.StartWithContinuations, MailboxProcessors that spin up 100,000 mailbox processors on a laptop, and a scaling agent that spawns per-URL workers to process lists concurrently. Remoting uses Cricut (f.actor) with actorHost.start and TCP transport, examples include ping/pong actors, supervisor patterns for automatic recovery, and an email-processing prototype that retries or replaces failed messages.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 2:22Events
- 5:30Async workflows
- 13:24Actors
- 19:57Cricket
- 23:14Resilient
- 25:45Start with continuations
- 30:23Email example
- 34:27Elastic example
- 41:38Resources
- 44:36CSharp Async
related talks
52mF# in the real world
46mFunctional programming in F# Fad or Fabulous
27mFour Principles of Reactive Architectures
01h 14mFunctional Programming in F#: Fad or Fabulous?
48mReliable messaging in the world of actors
01h 03mSAFE Stack: The Pit of Success for Functional Web Programming
01h 00mFunctional-first programming with F#
44mLife after business objects. Confessions of an OOP veteran