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

Our Reactive Future #22

Open
mattpodwysocki opened this issue Jan 13, 2016 · 0 comments
Open

Our Reactive Future #22

mattpodwysocki opened this issue Jan 13, 2016 · 0 comments
Labels

Comments

@mattpodwysocki
Copy link

We hear a lot about reactive programming, but what is it? No, it doesn’t mean the Reactive Manifesto, and it’s not related to Facebook’s React. It’s simply a programming paradigm that is readily responsive to events, nothing more. In the JavaScript world, reactive programming is a way of life. As we build larger applications, event-driven reactive architectures become a mess of events passing and state management that is hard to reason with. Matthew explores how we can embrace reactive programming and offers patterns for building better systems. Along the way, he explains how to handle state management, how to avoid race conditions between events, how to handle errors, and how to recover from errors and retry. You’ll leave knowing how reactive programming patterns can help build more robust applications.

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

No branches or pull requests

2 participants