My opinion.
I am a DO user and I don't think you can use it for production application. Casual hosting is fine.
For production servers, deterministic backups are very important. DO does not provide that. I faced a lot of issues when transitioning my server from non-backup to backup mode. To do that, you need to take a snapshot(server shutdown is required for this)of server. Then, you need to destroy it to get the same ip. There is a chance that your ip may go to someone else & any services that are dependent on ip may need changes. I was lucky to loose the ip for a while & get it back after some trial & error.
Also, you don't have any control on the backup. It is taken by the system and is supposed to be anywhere between 2-3 days.
Are those the only backups you take? I have all of my code stored in git, and my database (and assorted files) get backed up each night to aws. I figure a snapshot is my first line of defense, and aws is my backup in case this doesn't work.
For production servers, deterministic backups are very important. DO does not provide that. I faced a lot of issues when transitioning my server from non-backup to backup mode. To do that, you need to take a snapshot(server shutdown is required for this)of server. Then, you need to destroy it to get the same ip. There is a chance that your ip may go to someone else & any services that are dependent on ip may need changes. I was lucky to loose the ip for a while & get it back after some trial & error.
Also, you don't have any control on the backup. It is taken by the system and is supposed to be anywhere between 2-3 days.