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/o

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.