4 ms·
> You start with a monolith. I think that is the HN syndrome; people start projects like they will be larger than facebook even though the project will probabl
by tluyben2 6y ago
> You start with a monolith.
I think that is the HN syndrome; people start projects like they will be larger than facebook even though the project will probably never launch and if it does, get more than 10 users. Yet it runs all services aws has to offer and has 100 microservices and the little company(‘s investors) are paying through the nose in both dev time and hosting while a raw php script on a $1/mo vps would’ve been sufficient to validate the idea and get to ramen profitability and (far) beyond. Like someone said in another thread; focus on your market and acquisition channels first, build great stuff (much) later.
- nine_k 6y agoI remember that eBay seriously rewrote their backend three times — not because they kept doing it wrong, but because they grew. An architecture that fits well for a small company is inadequate for a large company, and vice versa.
- collyw 6y agoI bet there are orders of magnitude more cases where a ton of time and effort has been put into scalable architecture when it wasn't needed. Ebay is a serious outlier when it comes to scale of software, most people aren't going to serve anywhere near as many customers.
- zimpenfish 6y agoI've been through a couple of iterations of "MONOLITH BAD!" where none of the issues were monolith related but instead database design and usage. Also an iteration of "MICROSERVICES GOOD!" where there are more microservices than entire company employees (not just devs) and yeah, it's a bad idea at this scale.