search

Layr-Labs / eigenda-proxy

Secure and optimized communication layer for rollups using EigenDA.
MIT License
15 stars 22 forks source link

Support redis backend for memstore #72

Closed epociask closed 2 months ago

epociask commented 3 months ago

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.

samlaf commented 2 months ago

@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?

epociask commented 2 months ago

@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.

epociask commented 2 months ago

closed by https://github.com/Layr-Labs/eigenda-proxy/pull/111