> if you work at a startup or early stage company, it is nearly always the better decision to throw more disk space at a storage problem like this than worry ab

> if you work at a startup or early stage company, it is nearly always the better decision to throw more disk space at a storage problem like this than worry about optimizing for size. Developers are expensive, disk space is cheap This is great advice. In general at the beginning it is better to keep things as simple as possible. At one fast growing startup I worked at, one of the founders insisted we kept upgrading just one machine (plus redundancy and backups). It was a great strategy! Kept the architecture super simple, easy to manage, easy to debug and recover. For the first 5 years of the company, the whole thing ran on one server, while growing exponentially and serving millions of users globally. After seeing that, it’s clear to me you should only upgrade when needed, and in the simplest, most straightforward way possible.