Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Embracing Our Reactive Future #78

Open
mattpodwysocki opened this issue Jul 8, 2015 · 0 comments
Open

Embracing Our Reactive Future #78

mattpodwysocki opened this issue Jul 8, 2015 · 0 comments

Comments

@mattpodwysocki
Copy link

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant