> What happens if that EC2 instance dies suddenly or your EBS disk disappears, do you have point-in-time recovery for that DB?
Nah, and that's a bit of a hassle. Yesterdays data will do in a pinch (they'll have to manually rekey a days worth of data and some might get forgotten, but that's what stocktake is for).
That said, it's been running continuously for 3.5 years without downtime so far.
> What about if you get an influx of traffic and suddenly need to scale beyond what a single server can do (which is admittedly pretty high).
This particular app serves a small business, and I'm quietly confident they'll contact me before adding more than 100x their current staff overnight. It's currently running on a t3.micro, but I'd expect upgrading to a p4d.24xlarge with 1tb ram, 8gb NVME storage and 96 vCPUs will handle it if they do.
> How about logging
If I want to read the log files, I ssh in and read them. Sometimes I even scp them to localhost.
> deploys of a live copy of your site for each feature branch
I don't need that for a project with one developer and one stakeholder - I can just share my screen and walk him through what I'm changing.
Having at least a tiny bit of DevOps knowledge can save you a ton of money. Actually setting up GitHub Actions with a special SSH key-pair just for the deploy in GitHub Secrets took me a few hours from 0 to full deploy of code. I haven't seen the code to build before as I was at that time just consulting, I was sick and haven't known GitHub Actions until then. The same setup runs for a year already, I joined the company in the meantime :-) We can push to production or staging (different machines) and it just works for what we need.
Heroku is great, if you just want to start with something and show a proof of concept. As soon as you are doing more than just that you will probably get the first steep bills (at least from my point of view). We actually migrated from Heroku just a bit more than a year ago.
Nah, and that's a bit of a hassle. Yesterdays data will do in a pinch (they'll have to manually rekey a days worth of data and some might get forgotten, but that's what stocktake is for).
That said, it's been running continuously for 3.5 years without downtime so far.
> What about if you get an influx of traffic and suddenly need to scale beyond what a single server can do (which is admittedly pretty high).
This particular app serves a small business, and I'm quietly confident they'll contact me before adding more than 100x their current staff overnight. It's currently running on a t3.micro, but I'd expect upgrading to a p4d.24xlarge with 1tb ram, 8gb NVME storage and 96 vCPUs will handle it if they do.
> How about logging
If I want to read the log files, I ssh in and read them. Sometimes I even scp them to localhost.
> deploys of a live copy of your site for each feature branch
I don't need that for a project with one developer and one stakeholder - I can just share my screen and walk him through what I'm changing.