When NgRx is overkill in Angular - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is NgRx in Angular?

NgRx is a library for managing state in Angular apps using a Redux-inspired pattern with actions, reducers, and a single store.

beginner

When might NgRx be considered overkill?

NgRx is overkill when your app has simple state needs, few components sharing state, or when local component state is enough.

beginner

What are simpler alternatives to NgRx for small Angular apps?

You can use Angular's built-in services with BehaviorSubject or simple component @Input/@Output bindings for small or simple state needs.

intermediate

Why can using NgRx in small apps slow down development?

NgRx adds boilerplate code and complexity, which can slow development if the app doesn't need advanced state management.

intermediate

What signs show your Angular app might benefit from NgRx?

Signs include complex state logic, many components needing shared state, undo/redo features, or time-travel debugging needs.

Which situation suggests NgRx might be overkill?

A App needs undo and redo features

B App has complex shared state across many components

C App has only a few components with simple state

D App requires time-travel debugging

NgRx is best for complex shared state. Simple apps with few components usually don't need it.

What is a simpler alternative to NgRx for small Angular apps?

A Using NgRx effects only

B Adding more reducers

C Using Redux outside Angular

D Using Angular services with BehaviorSubject

Angular services with BehaviorSubject provide simple state sharing without NgRx complexity.

What is a downside of using NgRx in a small app?

A It adds unnecessary boilerplate and complexity

B It makes the app faster

C It removes the need for components

D It automatically fixes bugs

NgRx adds extra code and complexity which is not needed in small apps.

Which feature is a good reason to use NgRx?

A Undo and redo state changes

B Simple form input handling

C Static content display

D Single component state

Undo/redo features require complex state management that NgRx supports well.

NgRx is inspired by which pattern?

A MVC

B Redux

C Observer

D Singleton

NgRx uses Redux's pattern of a single store, actions, and reducers.

Explain when NgRx might be too much for an Angular app and what simpler options exist.

Think about app size and state complexity.

List signs that show an Angular app would benefit from using NgRx.

Consider app complexity and features.