I have experience with MariaDB (mysql), but basically, you should use seeding and migration scripts to keep your database up-to-date with your app.
Most of the ORMs supports these. The problem comes when you have multiple instances of your api server and you would like to make a change to your database. You need to shutdown all of them to make the database change, otherwise your servers will fail. Adding a column to a table is costly.
Backups should be automated. You can easily create backups with some bash script and you can even upload it to dropbox or something just to be sure.
I think you are not talking about Facebook scale stuff so you can easily tell the visitors that the app/website is under maintainace for a while (database upgrade or system upgrade)
You shouldn't worry about this until you are not there. Once you reach that scale, you can worry about it ;)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Database is a problematic one.
I have experience with MariaDB (mysql), but basically, you should use seeding and migration scripts to keep your database up-to-date with your app.
Most of the ORMs supports these. The problem comes when you have multiple instances of your api server and you would like to make a change to your database. You need to shutdown all of them to make the database change, otherwise your servers will fail. Adding a column to a table is costly.
Backups should be automated. You can easily create backups with some bash script and you can even upload it to dropbox or something just to be sure.
I think you are not talking about Facebook scale stuff so you can easily tell the visitors that the app/website is under maintainace for a while (database upgrade or system upgrade)
You shouldn't worry about this until you are not there. Once you reach that scale, you can worry about it ;)