4 ms·
While i absolutely agree with the author, how does this line of thinking change when you start using AWS or something similar? I'm building a SAAS app at the mo
by avenoir 9y ago
While i absolutely agree with the author, how does this line of thinking change when you start using AWS or something similar? I'm building a SAAS app at the moment and a lot of these scaling decisions are incredibly easy to implement without imposing any significant costs in terms of maintenance (and money, a lot of times). This would've been a different story had i been using my own infrastructure.
- theptip 9y agoI think there's a key difference between building your architecture with plenty of headroom to scale (leaving plenty of low-hanging fruit), and actually implementing high-scale function before it's required. In a cloud environment, it's quite easy to be comfortable that you _could_ scale out to 10-100x of your current capacity, if you have to. But it's probably not worth proving that fact until you have some customers. Or put another way, being in a very flexible environment makes it even more of a no-brainer to delay building for scale, since you have so many free or nearly-free options there. Now of course, if you really do hit scale you'll have the fun problem of needing to optimize your spend, but you can probably delay thinking about that until well after you've proven product-market fit.