Suggest an editImprove this articleRefine the answer for “How does signal differ from observable in terms of reactivity?”. Your changes go to moderation before they’re published.Approval requiredContentWhat you’re changing🇺🇸EN🇺🇦UAPreviewTitle (EN)Short answer (EN)**The main difference** is in how they react and where they get data from: `signal` follows a pull model and always stores one current value, while `observable` follows a push model and is a stream of events with no stored value of its own. **Key point:** Signal is like a "living variable" in Angular, while Observable is a "stream of events" from outside.Shown above the full answer for quick recall.Answer (EN)ImageThe main difference is **in how they react and where they get data from**. | What | `signal` | `observable` | |---|---|---| | **Type of reactivity** | *Pull model* (pulls data when you read) | *Push model* (delivers data as it arrives) | | **Stores the current value** | Yes, always one | No, only a stream of events | | **How it updates** | Change via `set()` or `update()` | A new `next()` from the source | | **How to subscribe** | Just call `signal()` in the template or code | You need `subscribe()` | | **When to use** | Local component state | Asynchronous data, requests, streams | In short: **Signal** is like a "living variable" in Angular. **Observable** is a "stream of events" from somewhere outside.For the reviewerNote to the moderator (optional)Visible only to the moderator. Helps review go faster.