Is Redis worth migrating from mysql?

Question

MySQL

Question for the pros. Selection for reading in style: id request, then reading the desired field. Asynchronous writing, id lookup, number writing from 1 to 10000 Ordinal reading from 1 to 100 thousand. What do you think is the best solution for the above? Are radishes ideal?
The essence is simple, I am doing a project, being a project manager, there is no one to ask, I want to change the database, I need performance, the number of users depends on the number of write capabilities. Now our database is running on a relational database (muscle, innodb). I want to switch to a modern solution, such as a radish, with prospects for scaling, with the ability to replicate from a slave to a master and vice versa (now there will be 3 servers, 1 only a db master read write, the second is only read (very low consumption), the third is writing and sending from slave to the master of its part
Required write speed to the master from 2500 records per second, reading once per minute 100 thousand, multi-threaded, asynchronous writing.

Answer 1

You are PM (Project Manager), your task is to manage human resources, DO NOT go into development.
The task of the programmer, according to the rules you described, is to implement the functionality, however, he must choose the tools for this on his own, according to the TOR.
The fact that you have indicated a few numbers are architectural requirements and they are OUTSIDE of your competence.
You have specified the requirements for writing / reading, but what about the integrity, cost, complexity of implementation and support?
Redis is a key-value store (most commonly used as a cache and pub/sub router), MySQL is a relational database. It's like comparing a motorcycle and a truck, they are designed for different purposes.

Answer 2

So muscle and radish are in completely different functional rows, if you need a keyval, then it is logical that this is radish, if sql is muscle or postgres.
From your description it is not very clear what you are storing, if you just have an id + field, then a radish and a selection only by id, then the radish is the best.

Answer 3

I want to change db

at the behest of the left heel? :)
radish is a NoSQL store.
All records are stored as key - value i.e. there are no samples by parameter in principle, in the usual sense. Is that just search search.
All that you described is available in mysql. Nobody is stopping you from scaling it.
Are the figures from the ceiling or are there already such data?
What is wrong with mysql and why is it not a modern solution?

Answer 4

Judging by the description, Redis is definitely not suitable for you.
Even from MySql to Postgres, the transition will be "painful". If the project is large, you need to prepare yourself for the fact that it will take a long time.

Answer 5

Do not suffer from garbage, Mysql normally processes all its tasks, unless of course you write queries correctly and have a well-structured database.
Many large companies sit on Mysql, I speak from personal experience.