Organization of a database of football matches, taking into account the compositions and keeping statistics on the players. Is it correct to do on JSON + noSQL?

Question

JavaScript

I want to make a database of football players and football matches of my local football club. Those. collect statistics for about 20 seasons. Dates, scores, lineups, goal scorers - that's it. Approximately 20 football seasons and about 700 matches. All this is in paper form (sports newspapers, records) and I would like to structure it in electronic form. The choice fell on RethinkDB, as the most understandable noSQL database and JSON as a way to access it + node, js to automate all this stuff. All this is fenced with the help of their own crutches - through pain and a toaster. Perhaps there is a more universal way to build this kind of database, or are there any other tools for solving the problem?
The database, in general, is suitable and hosted locally, but, of course, hosting on the Internet will not be superfluous.
I apologize for the confusion, if you need clarifications on my part, I will gladly provide them.

Answer 1

If you are ready to be responsible for data consistency, manually calculate all statistics, monitor corrections in all places, are ready to write hundreds of bicycles for the simplest tasks and do other not very interesting things, then your choice is noSQL

Answer 2

sorry, but you have relational data, why use a non-relational database for them as the main storage?