In the Node.js world, reactive programming is a way of life. What do I mean by Reactive? Simply this, readily responsive to events, nothing more! No, it doesn't mean the Reactive Manifesto, nor React from Facebook.
As we build larger applications, event-driven reactive architectures become harder to reason about as it becomes just a mess of events passing and state management. Let's cut to the chase and talk about how we can embrace reactive programming and patterns associated with it to build a better system.
We can answer the following questions:
- How do we handle state management?
- How do we avoid race conditions between events?
- How do we handle errors?
- How can we recover from errors and retry?
Join us in the reactive future!
In the Node.js world, reactive programming is a way of life. What do I mean by Reactive? Simply this, readily responsive to events, nothing more! No, it doesn't mean the Reactive Manifesto, nor React from Facebook.
As we build larger applications, event-driven reactive architectures become harder to reason about as it becomes just a mess of events passing and state management. Let's cut to the chase and talk about how we can embrace reactive programming and patterns associated with it to build a better system.
We can answer the following questions:
Join us in the reactive future!