Architect is a team activity, not a person
medium.com2 pointsby dsgrillo0 comments
- losing customer data: the backup must be done frequently enough. So I'm not risking losing data.
- downtime: I'd expect that RDS could still go south as well, maybe less frequently, but still. In my case I start another VM, run again the container and apply the backup.
- data breaches: Of course one can misconfigure something here, but not sure how it'd be different using a managed database.
- 1 droplet with docker pre-installed from DigitalOcean
- clone directly the repo from github
- together with the code, I have a folder with a bunch of docker images (caddy, mysql, php, redis, etc.) that I can easily spin up.
- for any release, I manually ssh, git pull and run the migrations (if any) and manually rebuild any docker image if needed
- I have daily jobs that dumps and zip the entire DB to S3
- if I have some deployment that I know will break any functionality during deployment, I warn the users before and accept that downtime.
- never had to handle a "hard" rollback till now.
I opened a ticket with amazon explaining what happened, got a call from their support to confirm that the violated box was the product one and not the carrier one, and then got reimbursed by the end of the same day.