There is no real downside. I agree it does make sense to use it how your proposal says.
Since by definition Cache is something that shouldn't be relied on, if something wrong goes while putting data into Cache (connection error/out-of-memory/etc) you can still process the data not relying on cache's output. I think this is why Cache::put() is a method which is considered one-way mechanism not returning anything.
Sign in to participate in this thread!
We'd like to thank these amazing companies for supporting us