In the previous video, you learned some of the basics of Redux.

And I've provided preliminary information for

components in a React Redux application.

But now, you may be wondering, why should I bother using Redux in the first place?

Or, when should I actually use it?

Redux does add substantial overhead to your project and

expects you to follow some very explicit patterns.

So let's discuss some of the benefits you'll have when you incorporate

Redux into your applications.

But before we do that, I should also mention that Redux does not require

that you use React as your view library.

We simply chose to reuse the scoreboard app because reacting redux align

themselves almost perfectly.

And React provides a written familiar environment to work in.

First, let's start with a very common scenario in application development.

You've decided to build an application, and you've heard great things about react.

So you immediately start building components and

wiring up a really nice looking UI.

Your app is tested, regularly launched, and everything is going great.

So what could possibly go wrong?

Well, shortly after the successful launch of your app,

you realized that you need to make some changes to the app.

And that a number of changes involve sharing data across components

within the application.

Not only do you need to create the new UI components to support the new

development request.

But you also need to figure out a way to synchronize and

share data throughout the application.

Redux to the rescue.

Redux comes equipped with the facilities to provide a single source of truth for

your application.

Making it easier to keep your application state in sync, and

distribute state data in a predictable and deterministic way.

Resulting in a more reliable and stable application.

In other words, when you use Redux with React, Redux handles all your

data management while React only manages the presentation and the use of your app.

So now, we know that one of the primary benefits of Redux is

its ability to make applications more predictable, scalable, and

stable, but what other benefits are there?

Redux is considered to be an opinionated framework.

This means that Redux expects you to implement features a specific way.

Otherwise, you're app will not work as you would expect.

This is good for a couple of reasons.

First, it means that Redux should be implemented following a consistent pattern

making it easier for anyone familiar with Redux to look at another app using Redux,

and immediately feel right at home with the application structure.

Second, by following the design patterns recommended by redux.

It makes debugging and testing your application much easier because

application responsibilities are distinct and isolated.

Now that we've covered a few of the benefits of why Redux is a valuable

framework, it's time to jump into creating our project.

But before we do, I want to re-emphasize that React applications do

not require that you use Redux.

In fact, for a very simple react application or

a web application that only uses minimal React components, Redux is overkill.

So one of the things you should do before implementing Redux is make sure that

your application will benefit from using it.

There's a fantastic article about using Redux written by the creator of Redux,

that can be found in the teachers notes for this video.

So I encourage you to check that out, along with other information about some of

the powerful features and benefits that Redux will bring to your application.