4 ms·
I think this depends on the context. Let’s say Uber had a database problem, they hired a bunch of database people and they came to the conclusion “we just have
by SilverBirch 2y ago
I think this depends on the context. Let’s say Uber had a database problem, they hired a bunch of database people and they came to the conclusion “we just have to write our own… fine. I think that’s actually perfectly legit. What I see much more commonly though is people who don’t really know too much about databases have problems and rather than go off and hire/consult with experts, they just decide to build their own. That’s when you get into real trouble.
The dirty truth is that whilst yes, Uber faces challenges due its scale, it also faces few real limits on building superfluous shit because of their success.
- makestuff 2y agoYeah this smells like promotion oriented architecture. I have a hard time believing that a logistics company that built DynamoDB and uses it extensively can make it work but uber cannot. The 6m in savings does not properly account for things like ramping up new hires on some custom database, maintenance (what happens in 5 years when whatever language you wrote it in needs to be upgraded to a new version, or some dependency), and a host of other things. Yes the cloud is expensive, but the entire point of it is that you are offloading all of that underlying maintenance/feature work to a team that only does that all day every day and is very good at it.