3 ms·
Cool take, come back to me on how well this thinking worked when you start landing Enterprise customers and you suddenly need to 10x your talent pool. You use b
by kfk 4y ago
Cool take, come back to me on how well this thinking worked when you start landing Enterprise customers and you suddenly need to 10x your talent pool. You use bare metal servers? It will be a lot harder to find devops talent with k8s being a standard. You built your web app on a low code tool? It will be impossible to meet that edge case your big Enterprise client needs. Being scalable can be over thinking, or it can save you from losing customers, context matters and each startup is different.
- ebiester 4y agoI'm reminded of the system that ran on one bare metal application server and one database server (not including backups) that was replaced with 80 services and a 10x ops spend for production. It was also slower than the original system. Build your monolith with modules and APIs and split your applications, not your services. If you need to split a module out, your API just has another transmission protocol instead. As Paul Graham said, do things that don't scale.
- kfk 4y agoTalent is harder to scale than tech, context is important.