Is using one Redis database enough for a medium-sized project?

Question

PHP

Is using one Redis database enough for a medium-sized project? Or is it worth writing a functional for switching databases in a wrapper? It is interesting how much the use of several databases in one application is in demand. Redis seems to have been conceived as a way to quickly write and select, in order to save time and resources, as I understand it, switching a database is a costly procedure? Is she in demand at all?

Answer 1

In any case, it is better to cut down such functionality immediately, or leave a place for it.
It will be necessary \ Not needed - the tenth question.

Answer 2

A "medium-complexity project" is when it is not so difficult for a developer to implement it. It’s not difficult for someone to write a system like the same toaster in a reasonable time, but for someone it’s difficult to raise a simple blog on WP.
If we talk about the degree of load (in the form of the number of simultaneous users) on the system, then the concept of "average load" is also quite extensive.
On the other hand, even if we take some more or less certain number of users as the average load, then the question arises about the configuration of the server on which redis is located.

Answer 3

In general, strictly speaking, the radish is not a db, rather an advanced key-value storage, sampling and sorting is not its task. How to build even a not very complicated site on it, I honestly have no idea.