database - MySQL or NoSQL? Recommended way of dealing with large amount of data -

I have a database that uses a large number of users to store random long strings (up to 100 characters) Will go The table columns will be: userid, string and actual long string.

Then it will look great like this:

will be unique to the user and string for each user will be unique.

The app is similar to the ordinary todo-list app, so the average amount of each user will be 50 seconds. I'm using straddles so that the user can delete specific tasks at any time.

I think the Toodo app can end up with 7 million works in 3 years and scares me with MySQL.

So my question is that if this is the recommended way to deal with large amounts of data with a long string (every new task gets a new line)? And Is MySQL the right database solution to choose for this type of projects?

I have not yet received large amounts of data and I am trying to save myself to remove the future.

This is a very simple relational use case. I do not see the need for NOSQL here.

The table you present should work fine, but I will personally question the need for a mixed primary key as you would present it. Probably to apply the specificity to all records, I have the primary key on the string, instead of a compound primary key between the user ID and the string, I will place a regular index on the useride.

The reason for this is that you only want to ask the strid (either for deletion or updating), you always want to ask for both fields (or queries by each field) to take advantage of your area Adding to add different indices on string and user-side to enable, which means disk taken by disk and disk index in my memory).

As far as MySQL is the right solution, it really will have to be set for you. I would say that MySQL should not have any problem in handling tables with two million rows and 2 indexes on two integer ID areas. Assuming you have allocated enough memory to keep these indexes in memory. There is definitely a ton of information available to work with MySQL, so if you're just trying to figure out, then this would be a good option.