4 ms·

Looks like he’s storing data in the server’s file system, but I see no mention of backups. Hopefully there’s more than one copy of the data somewhere (or it’s n

• threeseed 4y ago
  Also the problem everyone makes with backups is that they don't regularly test them. At which point storing the files on S3 would have been far easier, quicker and safer.
  • once_inc 4y ago
    "Nobody wants to backup, everybody wants to restore." This very much. For backups, the great crunchtime isn't when you set up the backups and see them appear where you want them. Crunchtime is when your system is in turmoil, and you need to recover what you've lost. I've seen so many people claim their backups are in perfect order, only to lose data because something broke between setup and recovery.
    • lazide 4y ago
      Also, time to restore for many peoples solutions can be days or weeks (if something goes wrong). Oops if that means you’re down for weeks. For some businesses (SaaS), there is no point event trying to come back from that.
  • jaza 4y ago
    Indeed. In my experience, even if you don't use any other cloud service, do yourself a favour, and use S3 + Cloudfront (or equivalent) for static / uploaded files. Then, if and when you need to scale your web tier horizontally, you've solved what probably would have been your main blocker. Plus, as mentioned, there's your backups sorted. Plus, you'll never have to worry about running out of disk space. Plus, you're taking load off your web tier, for something it really doesn't need to handle itself. Plus, massive performance boost on serving those assets over a CDN. Plus, it's really cheap, most likely a fraction of the cost of your VPS(es) or dedicated box(es).