Explain caching and performance differences of computed signals versus method evaluations.
Skip to solutionKEEP THE
mediumFrontend
What is the difference between computed() signals and standard method/getter calls in templates?
840 views
01
Understand the problem
signalsperformance
02
Attempt it yourself
Sketch your approach before reading the solution — that's what interviews test.
Nudge consolestandby
Stuck? Beam a request up — the console returns a conceptual nudge that guides your logic without spoiling the implementation.
03
Study the solution
computed() signals compute derived state and cache their values, re-evaluating only when their dependency signals change. Standard template methods or getters evaluate on every single change detection cycle, potentially causing performance bottlenecks for heavy logic.
Solution ready — 2 min read
Classified // press E to declassify
04
Read the code
Caching values with computed()
import { Component, signal, computed } from '@angular/core';
@Component({
selector: 'app-cart-total',
standalone: true,
template: '<div>' +
' <p>Tax (Signals): {{ taxAmount() }}</p>' +
' <p>Tax (Method): {{ getTaxAmountMethod() }}</p>' +
'</div>'
})
export class CartTotalComponent {
subtotal = signal(100);
taxRate = signal(0.15);
taxAmount = computed(() => this.subtotal() * this.taxRate());
getTaxAmountMethod() {
return this.subtotal() * this.taxRate();
}
}05
Join the discussion
Discussion (0)
Sign in to join the discussion.
No responses yet. Be the first to share what you think.
Transmission complete // awaiting log
KEEP THE
STREAK ALIVE.
Dossier 30 of 121 decoded in the Angular track. One more won't hurt.