4 ms·
>> shoving it into a json screams of throw it at a disk and let the hardware deal with it Which...worked. For quite a long time. And required no dev effort. Fr
by lostcolony 5y ago
>> shoving it into a json screams of throw it at a disk and let the hardware deal with it
Which...worked. For quite a long time. And required no dev effort. Freeing devs up to focus on other things.
They did it as a POC, and it worked, better even than they had anticipated; why over-engineer it up front? Even when it turns out they are gonna need it (i.e., YAGNI no longer applies), they have been able to push off their "solve problems customers don't care about" to instead favor "problems customers do care about". That...seems like sound engineering to me?
- rob_c 5y agoSpeaking as someone who has had to fix things like this... When you reach capacity and it hits a screaming halt as the hardware capacity has been reached and performance doesn't collapse its completely gone. This is not about best use. Hell json file performance may be well within spec of the system requirements, but jumping up and down without perf numbers or specs is typical of sweep it under the carpet for a generation...
- tptacek 5y agoThat would be a good critique if it was was happening, but they gracefully transitioned from a JSON file(!) backend to etcd, and gracefully transitioned from etcd to sqlite. I'd say they're going to gracefully transition from sqlite, but I think the think people don't have their heads around is that it's possible they'll never need to do that, because of The Unreasonable Effectiveness of SQLite.