Building Reactive Architectures with Functional Reactive Programming
Programming is essentially driven by certain mental models such as Structured Programming, Declarative Programming and Functional Programming. Most Problems can be solved using any mental model. In structured programming, it is the program's structure that subsumes the functions and procedures. Whereas in Functional Programming, it is the functional nature of the program that subsumes the structure. In this talk, we will explore the mental models of Functional Reactive Programming and how we solve problems within that mental model. There may be certain classes of problems such as orchestration in a micro-services architecture, that could be modeled elegantly using FRP paradigm. We will demonstrate solving the orchestration problem as an example to illustrate the mental models and its elegance in such a scenario.
Outline/Structure of the Demonstration
- Outline of our FR journey, and why we think we should have gone functional
- Here's why adopting FR is a bad idea
- Event Storming the Case Studies
- The building blocks for thinking in FR - observables, operators, subjects, functions and actors
- Mental Models to work with
- "Actors are to Observables what APIs are to functions"
- Containers or Serverless
- Impedance mismatch, the need for a ubiquitous FR actor framework, and why it should be based on Functional Programming
Participants will be able to think Functional Reactive, and understand its application for design as well as implementation.
Developers and Architects working in Product Development teams
Prerequisites for Attendees
Anyone who has good understanding of development and engineering