-
The scenario begs for a solution that will handle intermittent ProvisionedThroughputExceededException errors. In programming, you can think of it as implementing a try and catch logic. DAX only saves RCU when reading in cache objects but not for cache misses since new updates inserted into the table are not automatically reflected in the DAX cluster. You’re implying that one should cache the objects to get around the RCU limitation. That is not the main objective of using DAX. You should also consider the workload, the manner, and the frequency with which data is retrieved.
