5 ms·
From the article, individual video segments were 2-6 MB in size and SQS and Kinesis have a 1MB limit for individual records so they couldn’t have used either se
by alex_smart 11mo ago
From the article, individual video segments were 2-6 MB in size and SQS and Kinesis have a 1MB limit for individual records so they couldn’t have used either service directly. At least not without breaking their segments into even smaller chunks.
- Gasp0de 11mo agoYou're right, I didn't pay attention there. Still seems that there a many solutions better suited than S3. Probably a classic case of "We need an MVP fast, let's optimize later".
- 0x6c6f6c 11mo agoAgreed, but this isn't always bad. Optimizing early with unclear requirements can kill time, which at an early stage is just delaying product launch. Migrate/optimize later when you're actually reaching scale is a perfectly reasonable approach. In fact, if you have a decent abstraction or standard in place (e.g. S3 API or repository pattern) you can swap it out in place.