How to organize continuous service development?

Question

Work organization

Colleagues, plz explain the situation:
There is a service in which there are now about 1000 active users (they log in every day). Every hour, certain data is aggregated in it using different apis and added to the database.
The service should develop, we have planned small releases every 2 weeks. Therefore, the question arose about the organization of the development process.
Development goes on daily and affects both the files and the database.
Will git solve the issue (but it seems that only files are tracked there)? Or are there any other solutions? Who decides how to deal with such a situation?
Thank you!

Answer 1

For git code, for databases - migrations.