How to design a project database correctly?

Question

Database design

How to learn how to properly design databases for any projects? Are there any books, video courses, etc., where you can learn this? In principle, in all my projects I organize a database and work with it, but it seems to me that it will be difficult for other developers to understand the structure of my database and code, but now we are talking about the database. I personally think that this is a very important point, and the better the database is organized, the easier it will be to interact with it from the application. The topic of database archiving is also interesting, not backup, but archiving, in this context, the word "archiving" should be understood as organizing the storage of various old data, for example, 5-10 years ago, especially when about 20 such data is collected per year. 30 thousand lines. And in what cases archiving takes place.
PS Web project practice is preferred, but I don't think a web project database is fundamentally different from a native application database.

Answer 1

There are a lot of books and courses and videos on Youtube.
The design question varies from project to project and there is no single answer.
In order to make it clear to other developers, it is enough to name the tables in an adequate manner (i.e., the name of the table should clearly indicate its purpose, naming in the same style - or all tables are named in the plural or not (category, article or categories, articles) ) + You can make a file with a description of the tables.
Something like this

Answer 2

organization of storage of various old data, for example, 5-10 years ago

Depends on the DBMS. There are built-in ways: partitioned tables .

Answer 3

Probably teach theory.
There is even a special term for proper database design - "normalization".
As for archiving...
Each vendor offers its own solutions, but you can also invent your own wheel.
Depends on the specific task.