3 ms·
Perhaps but I think most of us have never worked on a problem of Uber's scale. The behaviors of things change spectacularly above a certain level; it's not just
by bdcravens 2y ago
Perhaps but I think most of us have never worked on a problem of Uber's scale. The behaviors of things change spectacularly above a certain level; it's not just the same thing times N.
The implicit assumption of "not invented here syndrome" is that it has been invented elsewhere already, which isn't always true.
- convolvatron 2y agowhats missing from the reuse picture for things like operating systems, compilers (somwhat), and databases is systems that use a 'lego' model of components that can be put together into solutions rather than deployable systems (which can clearly be built on top). this provdies room for doing real customization without having to build all the things from ground zero, and is likely to be more robust than trying to attach functionality fully on the outside like was done here. in the database world it would be really nice to implement caching and sharding extensions inside the transactional envelope