You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using redis would allow us to ensure that data isn't deleted when the instance is torn down. This will be especially useful for debugging / feedback cycles when engineering against a live rollup. Otherwise we'll have to reinstate the entire rollup if the proxy instance is terminated.
The text was updated successfully, but these errors were encountered:
@epociask this was my point. You added redis as a cache layer. But here's it's suggesting to add it as a replacement for memstore right? Why this separation between backends that store with Keys vs those that don't?
@samlaf this was an old issue filed before we introduced these newer abstractions. Technically we can achieve the same effect now by using a cache target with S3 for a memstore backend.
Using redis would allow us to ensure that data isn't deleted when the instance is torn down. This will be especially useful for debugging / feedback cycles when engineering against a live rollup. Otherwise we'll have to reinstate the entire rollup if the proxy instance is terminated.
The text was updated successfully, but these errors were encountered: