2 ms·
I have a more practical take on self hosting. Developers should be talking to the Ops folk. It informs your architecture decisions with practical consideration
by hinkley 5y ago
I have a more practical take on self hosting.
Developers should be talking to the Ops folk. It informs your architecture decisions with practical considerations, like physics, and how many NICs you can plug into a homogenous switch before you have network hops screwing up your pretty but naive designs.
When you stop self hosting, the number and quality of those people goes away when they realize they should find someplace else to be. And when we need fewer of them, we stop making new ones.
I try to push architectures that allow for a degree of heterogeneity, where we have one data center we own, and use others we don’t for geographic redundancy and speed of light concerns.
For a read mostly system 5a Reading an entire zip file's contents and writing out a brand new zip file could be an extremely slow process.
For read-mostly systems, that may mean for instance that we keep the system of record (I’m doing just this to bootstrap a personal project that has a read-mostly information architecture) but distribute the UI out into the Someone Else’s Computers.