> you basically have built-in Redis with Erlang's ets The big difference there is if you have a Dockerized app, Redis won't be restart on every deploy but the

> you basically have built-in Redis with Erlang's ets The big difference there is if you have a Dockerized app, Redis won't be restart on every deploy but the BEAM will be so you will lose your ETS cache or whatever you're storing. Now, I know cache is meant to be disposable but this model of using ETS instead of Redis reminds me of a Python or Ruby app storing its cache in memory. I mean, sure you can do it but for the longest time (7-8 years?) the community as a whole kind of landed on keeping that stuff out of your app's process.