4 ms·
> their own key-value store It seems like everyone does that. and it makes sense cause if given any chance to do it I'd jump on it immediately.
by iamasoftwaredev 7y ago
> their own key-value store
It seems like everyone does that.
and it makes sense cause if given any chance to do it I'd jump on it immediately.
- hintymad 7y agoNot in 2015/2016 when so many choices were already available, and certainly not in an org where MySQL would just be more than enough to meet Uber's need. Besides, Uber built their version on top of MySQL following pretty much FriendFeed's design: https://backchannel.org/blog/friendfeed-schemaless-mysql https://backchannel.org/blog/friendfeed-schemaless-mysql. A strange choice by itself given that better solutions had popped up left and right during the 6 years since the blog was published. Uber switch to Schemaless from a Postgres cluster, claiming that Postgres "does not scale for Uber". I see irony in that piece of Uber history. Particularly, Uber always claimed that some OS solution "had serious reliability issues". Cassandra in 2014 worked for companies that had orders of magnitude of traffic, yet Uber found it unusable. Similarly, Uber switched from MySQL to Postgres and then from Postgres to MySQL. Each time Uber published an article to claim engineering victory. The truth is that any of the three systems would be perfectly fine for Uber. Oh, didn't someone also claim that Elaticsearch crashed under Uber's load" and JVM-based systems were not usable for Uber's scale? " before Uber ended up adopting Elasticsearch? What really happened was that some teams in Uber simply didn't want to dive deep and produce objective tech assessment.
- iamasoftwaredev 7y agoI meant it makes sense that people keep building them needlessly because I would just at the opportunity even if I felt like it was totally pointless.
- deleted 7y ago[deleted]
- deleted 7y ago[deleted]
- hinkley 7y agoKV store as a concept seems to be a particularly Attractive Nuisance. It sucks people in like a pool without a fence around it. The Dunning-Kruger quotient is especially high. What I've always wondered is, why do people get so excited about working on ideas that they themselves characterize as 'simple'? The level of excitement around these sorts of projects does not match the level of rhetoric. You put the second rate people on the 'simple' stuff. You save some of the meaty bits for yourself. Which means that in your head, you know that KV stores are actually pretty complicated to get right. You either aren't admitting that to yourself or to the org or both. It just screams cognitive dissonance. Because if you were brutally honest and up front about it being complicated, you'd select a good one and have your fun elsewhere, say in using or scaling the KV system instead of building it.
- iamasoftwaredev 7y agoBecause "fuck you I actually want to fucking build something for once." anyway, more serious answer First off, what does this even mean? > The Dunning-Kruger quotient is especially high. ? > What I've always wondered is, why do people get so excited about working on ideas that they themselves characterize as 'simple'? It's not "simple", but it's doable. It's a problem that feels more approachable while still being difficult. That's the sweet spot, especially when you are trying to learn this stuff. It's the best way to learn. > Because if you were brutally honest and up front about it being complicated, you'd select a good one and have your fun elsewhere, say in using or scaling the KV system instead of building it. then I'm just another pleb using a KV system. Unless the rest of what I'm building is more interesting than the system I'm using then I don't really give a crap. It's boring.