| S3 has often fallen into a "catch all" solution for me whenever I need to store data large enough that I don't want to keep it in a database (RDBMS or Redis). Need to save a file somewhere? Dump it in S3. It's generally affordable (obviously dependent on scale and use), fast, easy, and super configurable. Being able to expose something to the outside, or with a presigned URL is a huge advantage as well. Off the top of my head, I think of application storage generally in this tier ordering (just off the top of my head based on the past few years of software development, no real deep thought here): 1. General application data that needs to be read, written, and related - RDBMS 2. Application data that needs to be read and written fast, no relations - Redis 3. Application data that is mostly stored and read - S3 Replace any of those with an equivalent storage layer. |