{"id":1180,"date":"2023-07-13T05:00:00","date_gmt":"2023-07-13T12:00:00","guid":{"rendered":"https:\/\/www.angulartraining.com\/daily-newsletter\/?p=1180"},"modified":"2023-07-12T11:54:50","modified_gmt":"2023-07-12T18:54:50","slug":"using-services-to-cache-data","status":"publish","type":"post","link":"https:\/\/www.angulartraining.com\/daily-newsletter\/using-services-to-cache-data\/","title":{"rendered":"Using services to cache data"},"content":{"rendered":"\n

Yesterday, we saw that services are singletons that are created once for all and stay in memory as long as the application is open<\/a>. <\/p>\n\n\n\n

This makes our services the best place to store data that can be shared between multiple different components. Such services can use BehaviorSubjects<\/a> or Signals<\/a> to cache that data and replay the last value automatically to any new subscriber (component, directive, pipe, service, etc.). <\/p>\n\n\n\n

Here is an example using a signal to store a value and expose it in a read-only fashion:<\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n\n

<\/p>\n\n\n\n

This article compares BehaviorSubjects and Signals<\/a> to cache a shareable value.<\/p>\n","protected":false},"excerpt":{"rendered":"

Yesterday, we saw that services are singletons that are created once for all and stay in memory as long as the application is open. This makes our services the best place to store data that can be shared between multiple different components. Such services can use BehaviorSubjects or Signals to cache that data and replay […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,21],"tags":[],"class_list":["post-1180","post","type-post","status-publish","format-standard","hentry","category-angular","category-architecture"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t