top | item 45719872 (no title) Gasp0de | 4 months ago You'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". discuss order hn newest 0x6c6f6c|4 months ago Agreed, 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.
0x6c6f6c|4 months ago Agreed, 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.
0x6c6f6c|4 months ago
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.