title: DynamoDB vs S3 when using images
body: <p>When it comes to images, everyone says use S3. I understand different tools are built for different purposes it's understandable S3 is the default go to. But for educational purposes, I'm curious when it would be a better idea to use DDB over S3.</p>
  
  <p>Let's say for an app like tinder, can't you store the main profile image (let's say image1) in the ImageTable1 with highest read write capacity and the rest of 5 or so images in the respective tables with low read write capacity settings. Each of these tables would only require a Hash Key and not a sort key.</p>
  
  <p>Or is this design still a bad idea? Wouldn't this design cost less than using S3 since S3 pricing is proportional to number of get put requests while DynamoDB pricing is based on preset read write capacity?</p>
  
  <p>And yes, I'm very aware that DDB has a single item size limit of 400kb. So for this argument, let's assume each image is &lt;400 KB. </p>