3 ms·
Out of curiosity what do you find wrong in the s3 solution? This is a data volume that rdbms can manage, but are you looking specifically for the engineer to sa
by lumost 2y ago
Out of curiosity what do you find wrong in the s3 solution? This is a data volume that rdbms can manage, but are you looking specifically for the engineer to say something like “I’ll maintain a Write Ahead Log in the database”
- eastbound 2y agoIt’s just that it’s easier to pull if it’s in the same db as everything else. The S3 solution is perfectly ok and 10x cheaper (.20$ pm instead of 2$), but the difficulty is, now you need to do a REST call to S3, and if you want the history per user or per day or per object, then you need to design all sorts of metadata to be able to fetch the right objects.