What architecture to choose for a web service?

Question

Do it yourself

Started learning web programming with the goal of making a web service. The question of architecture immediately arose - which frontend and backend to choose.
The web service allows you to solve tasks, for example, mathematical examples, while statistics are recorded, such as: the percentage of correctly solved tasks, the time spent on solving one task. The service also involves users uploading files (images and text documents) to the site. The service displays tasks to the user according to his past statistics, for example, tasks of a certain category are most difficult for the user, respectively, more such tasks come across to him. Yes, hardcore.
It is desirable that at the peak it can withstand loads of 1000-1500 users, with 1-2 servers.
I apologize right away for the vagueness of wording and inaccuracies, however, I want to learn by implementing the project in practice, coping with difficult moments along the way.

Answer 1

Well, on the web, the most common is MVC, but in general, you can choose anything. MVC is easy to use.