Re:Pelikan, Twitter’s framework for building caches
by thinkingfish on Tuesday October 04, 2022 @09:45PM
(#33090005)
It was supposed to be a bit tongue-in-cheek... Obviously nobody should create a pingserver just for the sake of with the specs we had. But, as a halfway marker to a production-ready cache service, it's good to have something that lets you test the parts that will account for well over 50% of the CPU time in production.
Re:Pelikan, Twitter’s framework for building caches
by systemvoltage on Wednesday October 05, 2022 @12:35AM
(#33091289)
Yea definitely, 90% of the time it meant to be positive; just totally shocked by how badly engineered Juicero was.
> an over-engineered...
Ever since I saw Juicero teardown by AvE [1], I'll never see the term "over-engineered" in a positive light. Usually that means, it is sub-optimal and not engineered well, usually in a hurry and developed with a broad brush approach towards safety margins. Juicero was so over-engineered, it was embarrassing.
[1] https://www.youtube.com/watch?v=_Cp-BGQfpHQ