Don’t Use Storable Actions in Promises
The framework stores the response for storable actions in client-side cache. This stored response can dramatically improve the performance of your app and allow offline usage for devices that temporarily don’t have a network connection. Storable actions are only suitable for read-only actions.
Storable actions might have their callbacks invoked more than once: first with cached data, then with updated data from the server. The multiple invocations don't align well with promises, which are expected to resolve or reject only once.
Should that deter me from using promises with the following use cases:
I have to retrieve the current user information across multiple components before I allow a callback to the server.
I also have to grab the entire role hierarchy to determine the roles above the user in order to determine the public group relationships from the group member table.
Both sets of this info would remain relatively static and would likely benefit from storable actions. If I do this across 4-5 components on the same app page, I think that would degrade performance, especially in the latter use case. How much of a hit would be taken from using a storable actions with promises, if any?