Async in Redux Workshop: Module 5

Transcript

1. MODULE 5: ASYNC WITH GENERATORS AND SAGAS
2. WHAT IS A GENERATOR?
3. GENERATORS ▸ Generators are functions which can be exited and later re-entered. Their context (variable bindings) will be saved across re-entrances. ▸ Generators have 2 parts: a generator function and generator object ▸ Generator objects have a `next()` method that returns on object with `value` and `done` attributes
4. SIMPLE EXAMPLE
9. ASYNC GENERATORS: HTTP://BIT.LY/ASYNC-GENERATOR
10. REDUX-SAGA
11. REDUX-SAGA ▸ A Redux implementation of the Saga Pattern. ▸ Based on generators. ▸ Instead of dispatching Thunks, you create Sagas to gather all your Side Effects logic in a central place. ▸ This means application logic lives in 2 places: ▸ Reducers are responsible for handling state transitions between actions. ▸ Sagas are responsible for orchestrating complex/asynchronous operations.
12. SAGA PATTERN ▸ Saga is a failure management pattern. ▸ Sagas are multiple workflows, each providing compensating actions for every step of the workflow where it can fail. ▸ You can think of Sagas as daemons, a long living process for orchestrating transactions and handling recovery from failures.