Signal vs observable comparison in Angular - Quick Revision & Key Differences

Recall & Review

beginner

What is an Angular Signal?

A Signal is a reactive primitive in Angular that holds a value and notifies when the value changes. It is used for simple reactive state management with synchronous updates.

beginner

What is an Observable in Angular?

An Observable is a stream of asynchronous data that can emit multiple values over time. It is used for handling events, HTTP requests, and other async operations.

intermediate

How do Signals differ from Observables in Angular?

Signals provide synchronous, simple reactive state with immediate value access, while Observables handle asynchronous streams and require subscription to receive values.

intermediate

Can Signals emit multiple values over time like Observables?

No, Signals hold a single current value and notify on changes synchronously. Observables can emit many values asynchronously over time.

intermediate

When should you prefer Signals over Observables in Angular?

Use Signals for simple, synchronous state management inside components. Use Observables for complex async data streams like HTTP calls or event handling.

Which Angular feature provides synchronous reactive state with immediate value access?

A Observable

B Signal

C Promise

D EventEmitter

Signals hold a current value and notify synchronously, unlike Observables which are asynchronous streams.

What must you do to receive values from an Observable?

A Subscribe to it

B Call it directly

C Use a Signal

D Assign it to a variable

Observables require subscription to start emitting values.

Which is better for handling HTTP requests in Angular?

A Observable

B Template reference

C Signal

D CSS variable

Observables handle asynchronous data streams like HTTP requests effectively.

Signals in Angular are primarily used for:

A Styling components

B Asynchronous event streams

C Synchronous state management

D Routing

Signals provide simple synchronous reactive state management.

Which statement is true about Observables?

A They are only used for styling

B They hold a single current value

C They update synchronously

D They emit multiple values over time

Observables emit multiple asynchronous values over time.

Explain the main differences between Angular Signals and Observables.

Think about how each handles data and timing.

Describe scenarios where you would choose Signals over Observables in Angular development.

Focus on simplicity and sync needs.

Practice

1. Which statement best describes an Angular signal compared to an observable?

easy

A. A signal requires manual subscription to receive updates.

B. A signal handles multiple asynchronous events over time.

C. A signal holds a single reactive value and updates UI automatically.

D. A signal is used only for HTTP requests.

Solution

1. Step 1: Understand what a signal represents

   Signals hold a single reactive value that updates the UI automatically when changed.

2. Step 2: Compare with observable behavior

   Observables handle streams of data over time and require subscriptions, unlike signals.

3. Final Answer:

   A signal holds a single reactive value and updates UI automatically. -> Option C

4. Quick Check:

   Signal = single reactive value [OK]

Hint: Signals hold one value; observables handle streams [OK]

Common Mistakes:

• Thinking signals handle multiple async events like observables
• Believing signals require subscriptions
• Confusing signals with HTTP request handlers

2. Which of the following is the correct way to create a signal in Angular?

easy

A. const count = new Observable(0);

B. const count = signal(0);

C. const count = subscribe(0);

D. const count = createObservable(0);

Solution

1. Step 1: Recall Angular signal creation syntax

   Signals are created using the signal() function with an initial value.

2. Step 2: Identify incorrect options

   Observable creation uses new Observable(), subscribe is a method, and createObservable() is not valid.

3. Final Answer:

   const count = signal(0); -> Option B

4. Quick Check:

   signal() creates signals [OK]

Hint: Use signal() function to create signals [OK]

Common Mistakes:

• Using new Observable() to create a signal
• Confusing subscribe() with signal creation
• Using non-existent createObservable() function

3. Given the code below, what will be logged to the console?

const count = signal(1);
count.set(5);
console.log(count());

medium

A. 1

B. An error because signals cannot be set

C. undefined

D. 5

Solution

1. Step 1: Understand signal value update

   The signal is created with initial value 1, then updated to 5 using set().

2. Step 2: Check the value returned by calling the signal

   Calling count() returns the current value, which is 5 after set().

3. Final Answer:

   5 -> Option D

4. Quick Check:

   Signal value after set() = 5 [OK]

Hint: Calling signal() returns current value [OK]

Common Mistakes:

• Assuming initial value remains after set()
• Thinking signals cannot be updated
• Confusing signal() call with observable subscription

4. What is wrong with this Angular code using an observable?

const obs = new Observable(subscriber => {
  subscriber.next(1);
});
obs.next(2);

medium

A. Observables do not have a next() method on the instance.

B. Observable must be created with signal() instead.

C. Subscriber function cannot call next().

D. Observable must be subscribed before calling next().

Solution

1. Step 1: Understand Observable instance methods

   Observable instances do not have a next() method; next() is called on the subscriber inside the constructor.

2. Step 2: Identify misuse of next() outside subscriber

   Calling obs.next(2) is invalid and causes an error.

3. Final Answer:

   Observables do not have a next() method on the instance. -> Option A

4. Quick Check:

   next() is on subscriber, not observable instance [OK]

Hint: next() is called inside subscriber, not on observable [OK]

Common Mistakes:

• Trying to call next() on observable instance
• Confusing signal() with observable creation
• Believing subscription is needed before next()

5. You want to manage a simple counter state that updates the UI immediately when changed. Which approach is best and why?

Option A: Use a signal to hold the counter value.
Option B: Use an observable and subscribe to updates.
Option C: Use a Promise to fetch the counter value.
Option D: Use a BehaviorSubject without subscription.

hard

A. Signal is best because it holds a single reactive value and updates UI automatically.

B. Observable is best because it handles multiple async events efficiently.

C. Promise is best because it resolves once with the counter value.

D. BehaviorSubject without subscription updates UI automatically.

Solution

1. Step 1: Identify the requirement for simple immediate UI update

   A simple counter state that updates UI immediately fits the signal use case.

2. Step 2: Compare other options

   Observable requires subscription and is better for streams; Promise resolves once; BehaviorSubject needs subscription to update UI.

3. Final Answer:

   Signal is best because it holds a single reactive value and updates UI automatically. -> Option A

4. Quick Check:

   Simple state + auto UI update = signal [OK]

Hint: Use signals for simple reactive state, observables for streams [OK]

Common Mistakes:

• Choosing observable for simple state without subscription
• Using Promise for reactive UI updates
• Assuming BehaviorSubject updates UI without subscription