Is it worth running only one redis container if it is used by applications in containers from different projects?

Question

Redis

The server hosts several web projects that run in docker containers. I am running them via docker-compose.
I took the DBMS out of the container into mysql which runs on bare metal, because I realized that the DBMS in the container is a bad idea. Now applications in containers access mysql directly and not the container.
The question arose, maybe it makes sense to do the same with redis?

Answer 1

I think the main thing here is that radishes are used by applications from different projects. There is no authorization (access rights) in radish, so these applications may well interfere with each other (for example, flushall during maintenance will clean up the database of all these projects).
The second point: the radish is single-threaded, which does not allow it to simply scale to all server cores. I know a successful experience when docker made it easy to manage 12 radish instances on one old wheelbarrow (much easier than through systemd and so on).
So the reasons for:
* isolation
* scaling
"Against" in the comments have already sounded.