Channels in Redux-saga

What are the channels? Are they useful to us in day to day programming? We’ll be going through this blog that channels are played really a major role in redux-saga.

Channels:
Channels are of 3 types which are used to perform 3 different things, here I will brief you about those channels here but will explain in detail a bit later.

Action Channels: Action channel is a buffer, it stockpiles actions which sagas can consume one by one.
Generic Channels: Generally, we use Generic channels to communicate between two sagas. This can be done through the Actions but the idea of a channel is that communication is limited interest in sagas without other sagas being privy to that information.
Event Channels: Event Channel is completely different used to wrap outside event sources. we can consider web socket as a good example of the Event channel.

#react #redux #saga #redux-saga

Channels in Redux-saga

What are the channels? Are they useful to us in day to day programming? We’ll be going through this blog that channels are played really a major role in redux-saga.

Channels:
Channels are of 3 types which are used to perform 3 different things, here I will brief you about those channels here but will explain in detail a bit later.

Action Channels: Action channel is a buffer, it stockpiles actions which sagas can consume one by one.
Generic Channels: Generally, we use Generic channels to communicate between two sagas. This can be done through the Actions but the idea of a channel is that communication is limited interest in sagas without other sagas being privy to that information.
Event Channels: Event Channel is completely different used to wrap outside event sources. we can consider web socket as a good example of the Event channel.

#react #redux #saga #redux-saga

Terry Tremblay

1599736380

How to implement Redux Saga with ReactJS and Redux?

Intro to Redux setup tutorial

Very often, you can hear about the state in frontend applications, but what it exactly is? Let me explain.

State in frontend applications represents all the data stored in the application in a given time. It can be stored in different formats like objects or strings. Based on the state’s values, we can personalize the application, display, and hide certain elements.

To manage the state in modern frontend frameworks, we can use different libraries like Redux, MobX, or NgRx. The most common one is Redux, which is used mainly with ReactJS applications, although it’s possible to use it with Angular as well.

With Redux, the state of the application is kept in the store, and we can access the store from every component in the application. Redux consist of store, reducers, and actions.

In this article, I’d like to tell you more about the Redux library and create a simple ReactJS project, where I’ll set up a Redux step by step.

Let’s start!

How does Redux work?

Redux is based on the flux architecture, and it supports unidirectional data flow. It means that data in the application goes through the same lifecycle over and over again, which makes everything that happens in the state more predictable.

Let’s take a look at the simple graphic, which illustrates the data’s lifecycle in the Redux application.

Image for post

On the graphic above, you can see that from the UI, we trigger an action that passes the data to the reducer. Next, the reducer updates the store, which is the state of our application. The store defines the user interface.

Let’s think of the benefits which using Redux can bring to our development.

Benefits of using Redux

When you’re building the application, you know more or less how much data you will need to manage inside the application. In most cases, frontend applications have some functionality, and very rare they are just static websites. Commonly, we keep some user data, forms data, etc. inside the application state, and then it’s very useful to use a tool for managing the state.

The most popular solution in ReactJS applications is Redux. There are some important benefits to the popularity of this solution. Let’s take a look at them one by one.

predictable state — The state in Redux is predictable because reducer functions are pure; therefore, if we pass the same state and the same action, it needs to return the same result. Redux state is also immutable; it can’t be changed or modified.
easy to maintain — Considering that it’s predictable and very strict about the structure of the Redux application, anyone who knows Redux will understand it and work with it easily.
easy to debug — Redux allows us to log the behavior using available developer tools, makes debugging easier.
developer tools available — Redux has amazing developer tools, that can be used in the browser to see what’s happens in the backend.
server-side rendering — Redux supports server-side rendering by allowing to manage initial rendering. Redux sends the state of the application to the server with a response to the server’s request.

Above I listed a few benefits of using Redux to manage the state of your frontend application. Now, I’d like to go to the practical part, where we are going to set up a Redux with ReactJS application.

#javascript #react #redux-saga #frontend #redux