How many tables in the database does the Toaster project have?

Question

Database design

I have one project, I don't know if it's a project. It already has 55+ models, 49 tables in the database and their number is growing as well as the code in the controllers, as well as new packages, modules, libraries and much more.
By reducing the number of tables, for example, ORM will be violated, controllers and models will be clogged with unnecessary functions. For more control, I try to make models and everything in the spirit of OOP, for example, the User model I only have 4 tables and 3 additional models to manage the main model, because if you do everything in one, there will be 35+ columns and a huge pile of code in the model , flip through hundreds of lines. What is there to say about the controller.
Is this the norm? How many tables in the database does this project "Toaster" have? How many tables do projects like vk.com, facebook.com, google have?

Answer 1

Here it is impossible to answer unequivocally because everything depends on everything.
The same database can be organized differently depending on the task and architecture.
I am more than sure that such projects have huge databases and there are a lot of tables ... But the queries themselves are optimized, and most likely they do not use any ORM
. Plus, all sorts of replications are configured, query caches and a lot more ...

Answer 2

I worked on a project where there were about 300 tables. In fact, you only work with what you need now, so this does not add much complexity to development.