4 ms·

OK. But... some of us do need to use Cassandra? Some of us do need to use Kafka? Like, more than 5 companies definitely do work that requires that level of scal

OK. But... some of us do need to use Cassandra? Some of us do need to use Kafka? Like, more than 5 companies definitely do work that requires that level of scale... Of course bad engineers make bad engineering decisions, and most engineers are bad, but that isn't really interesting to point out imo. > How much data do you have exactly? Petabytes or exabytes at every company I've worked at, none of which are names mentioned in this article. > But have you done the math? Yeah. I mean, I've read this before, so I'm gonna stop here. I get it. Engineers are bad at their jobs so they default to picking the technologies they've heard of instead of the technologies that make sense. But like... working with massive amounts of data is not that rare anymore. It wasn't in 2017, it definitely isn't in 2022.

zcdziura 5y ago
You're essentially agreeing with the author's premise. They're saying that you should think about your business domain problem and choose technologies that solve that problem, even if they aren't the big, flashy technologies used by Big Tech. If your business domain involves handling peta/exabytes of data, then by all means Cassandra is right for you! Most companies don't handle nearly that much data however, so using Cassandra for a database to manage only a few gigabytes of data is overkill.
- staticassertion 5y ago
  Of course I agree with that. I just think that it boils down to: a) These tools are for companies that do XYZ b) Lots of engineers are bad at choosing tools both of which are pretty obvious. Except it also sorta makes this other point "you aren't Google" but... a lot of us actually do stuff at scale. A lot of us. A lot don't, I'm sure.