Contents
Can we mark an action as storable if it updates or deletes data?
Never mark as storable an action that updates or deletes data. Therefore, storable actions might have their callbacks invoked more than once: first with cached data, then with updated data from the server.
Does Lightning data service cache discrete Salesforce sObjects as well as any other type of response?
Unlike storable actions that can cache any type of response returned by an Apex method, the Lightning Data Service caches discrete Salesforce sObjects (record collections are on the roadmap). (See the Modularizing Code in Lightning Components post for strategies to implement a custom cache.)
What kind of caching algorithm do I Need?
In this case you would want a sort of hybrid caching algorithm. To handle the write data you might want something like Wise order of Writes (WOW) and an LRU algorithm for data that has been read from disk.
Which is the most efficient cache replacement algorithm?
If I recall correctly from my OS course, LRU is the best general cache replacement algorithm. But maybe I’m mistaken. Also, this is a bit of an academic question, since, generally, main memory is cheap and abundant and I don’t really need to worry about cache size too much.
Can a programmer make his own cache implementation?
Programmer 1 did make his own cache implementation using hashtable and that what he only knows about caching and his hashtable contains about 150 entry which he consider an extensive data (caching = hashtable, load the lookups in hashtable and everything will be fine nothing else) so lets see how will the interview goes.
Do you cache the result individually or combined?
LWC: Does @AuraEnabled (cacheable=true) cache the result individually or combined? Prequel: I have several methods in need of the same @wire operations. The approach I initially took was to make a new utilities component just for the wire operations and then use the pubsub library to fire the data that was retrieved.