Premium

Feature service with signals or RxJS vs NgRx Store for a large Angular product surface

Guided tradeoff battle · Updated Mar 30, 2026

A multi-screen Angular product surface has optimistic updates, websocket refreshes, draft restore, route re-entry, and several teams touching the same state graph. Would you keep state in a feature service with signals or RxJS, or move the core shared state into NgRx Store?

Keep core state in a feature service with signals or RxJS
Move core shared state into NgRx Store

What you’ll build / What this tests

This premium angular tradeoff battle focuses on Feature service with signals or RxJS vs NgRx Store for a large Angular product surface. Commit to a direction, justify it with the prompt constraints, and explain when the alternative wins.

Learning goals

Is this still one feature boundary or now a product…
How many event sources and transition paths exist?
How will engineers explain and inspect state changes later?
How many teams need the same mental model?

Key decisions to discuss

Pick a direction for this exact prompt, not the universal winner.
State the trade-off that matters most for this scenario.
Name when another option becomes the better answer.
Keep the explanation grounded in concrete constraints.

Evaluation rubric

Strong answers tie the recommendation to the prompt.
Good tradeoff reasoning explains downsides, not just upsides.
The answer should show when the recommendation stops being right.
Follow-up pressure should not break the argument.

Constraints / Requirements

Which direction would you defend for this prompt, and how would you explain when the other option is…
Fits best when the feature is still truly bounded, ownership is clear, and the team can…
Fits best when the feature behaves like a small product platform with many event sources, multiple…

Options on the table

Keep core state in a feature service with signals or RxJS: Fits best when the feature is still truly bounded, ownership is clear, and the…
Move core shared state into NgRx Store: Fits best when the feature behaves like a small product platform with many event…

Common pitfalls

Arguing from preference instead of prompt constraints.
Pretending one option is always the winner.
Ignoring the main downside of the chosen direction.
Failing to explain when the alternative becomes stronger.