reF#ACTORing using F# and actor model
summary
Shows how to apply the actor model using F# to refactor existing codebases: specifically uses F# language features and actor-based concurrency (actors) to restructure applications. Focuses on practical techniques and tools for migrating or redesigning parts of systems with actors in F#.
AI-written summary · about
chapters (4)
- 0:00Start
- 5:51Reasons to rewrite - functional changes Original system written for a single specific cloud storage provider, the new one should work with multiple storage providers Different file upload protocols (FTP vs. HTTP) Database polling to be fully replaced with message queues
- 8:12Reasons to rewrite-revised design goals - Avoid manual thread management Strict mutability control Enforced component isolation • Replace general-purpose programming model with the one tailored for message processing • Better exploit functional transformations
- 14:05Why F#? Just say "no" to mutable variables! Idiomatic F# API, actors as functions without any internal state *An actor in F# can be implemented as a finite state machine with each state managed by its own function • F# is made for functional transformations! •Less ceremony, more compact code
related talks
35mActors Design Patterns and Arrowised FRP
48mBuilding Reactive Services using Functional Programming
52mF# in the real world
37mLife After Business Objects: Confessions of an OOP Veteran
01h 07mPipe forward : Using Elixir and F# together
01h 00mF# in the Real World
44mLife after business objects. Confessions of an OOP veteran
25mSCALAZ 8 VS AKKA ACTORS
