Always scale vertically, not horizontally.
It’s easier for engineers to scale horizontally (e.g., adding all the nips to your client) because they can simply reuse infrastructure across different sectors. It's all very natural and comfortable. However, this means that the value grows linearly and fails to compound (different sectors don't work together). Scaling vertically (e.g., owning the best content production to consumption pipeline for one event kind) allows you to compound the gains your products offer for a single task, annihilating any competition that comes your way.
Login to reply
Replies (11)
mmm interesting. I wonder if this is actually true. Its not obvious to me that it is. But i am also retarded so maybe it is.
There you got the #unixPhilosophy .. just one thing that pipes to everything else ..
kiss.
reminds me libuv
(keep it simple stupid) before anyone jumps to concusions 🤣
Then you get systemmd to fuck everything up :)
🔥🚀 karrot 💜s
#slackware
hm, we callin software .. scaling now? 😁
damn, must be 2026. Servers though, horizonal is good and vertical bad mmkay
This XD
Even with in server-side software, doing a pipeline of things that all use each other is better for the user and thus can have a higher value and protect yourself against competition better than multiple servers that are kinda the same but serving different markets/users.
The "cloud" business model fucked us up. It's only good for Google/Microsoft/AWS.
#baobrain + #baomarkets took this path