jjirsa

29 ms·

121.
by jjirsa 9y ago
> and even if you do succeed, and have now hired a bunch of “rock stars,” you don’t have a team. You have a bunch of “rock stars.” In reality, rock stars typically don’t play well with others (consider these examples), and each member is
122.
by jjirsa 9y ago
I met one of their architects at a few Cassandra summits (2014 and 2015), so their talks should be online Here’s one: https://academy.datastax.com/resources/ing-groep-nv-exploiti... And another https://m.you
123.
by jjirsa 9y ago
You can run a bank without ACID SQL ING uses Cassandra, which has no single point of failure, has been around for almost a decade, and would have made gitlab’s mistake a nonissue (and almost certainly would have made this one a nonissue as
124.
by jjirsa 9y ago
Good move, will be good for the database for sure. I think of this article [0] every time someone says "why not just use <some hipster database written by 2 people over the course of a year>": Rule 1: Developing a good DBMS
125.
by jjirsa 9y ago
The strength of PHP is the fact that you can get php hosting for almost no money, that takes no effort to setup, is shared but isolated, and is almost always portable A programmers response is “I can throw Django in a container” or “I can j
126.
by jjirsa 9y ago
There exists a LOT of data models that don’t use auto incrementinf primary keys. Rarity or not, it’s a real use case and a real problem for master/master replication Also, even if you do use auto increment with offsets for each server,
127.
by jjirsa 9y ago
Exactly this. Whenever you collect millions of things, even at low resolution, it adds up quickly Collecting high resolution and filtering down to low resolution for lower importance is still difficult and can require petabytes for real wor
128.
by jjirsa 9y ago
Primary key conflicts are still a thing. Especially problematic where you're either not using auto_incrementing PKs, and/or you try to switch writes from one master to the other and app has to be aware of the switch.
129.
by jjirsa 9y ago
Show me a single person who runs 64TB on a single table on a single node, and I'll show you someone who will cry because of a prod failure sooner than later.
130.
by jjirsa 9y ago
Those people are objectively wrong.
131.
by jjirsa 9y ago
Quick, tell YouTube and Facebook they’ve been doing it wrong all along
132.
by jjirsa 9y ago
Many people ARE using petabyte scale databases. They don't start out that way, but they will be if they're successful, and if they're not they probably shouldn't be running their own databases anyway (go RDS it up or som
133.
by jjirsa 9y ago
Except the person to whom I replied said to use traditional SQL databases: > Traditional SQL databases end up being many times simpler in practice, and because of their inherent scaling limitations, much easier to manage. And most import
134.
by jjirsa 9y ago
Lots? Certainly most adtech firms and IOT type firms Also: scaling isn't just speed, it's also capacity, HA, failover. Are you running 100x4T NVME in a single server? Edit: fun little story. Some time back, I wrote a compaction st
135.
by jjirsa 9y ago
The reason people don’t start with a relational DB has nothing to do with the data model or query language - people choose databases like Cassandra because scaling to 500 Postgres or MySQL instances holding a combined petabyte of data is ho
136.
by jjirsa 9y ago
There is so much wrong with this post I don’t know where to start Old school sql replication is awful. It’s awful in Postgres (single threaded replay? A single vacuum can make your slaves fall behind). It’s awful in MySQL (go ahead and tell
137.
by jjirsa 9y ago
If SSDs solve your scaling problem, you never had a scaling problem
138.
by jjirsa 9y ago
So there’s the “how”, where’s the “why”? Why Hurd and not Linux? Or one of the BSDs? Or any of the thousands of OSS projects actually useful to real people in 2017?
139.
by jjirsa 9y ago
Reminder that FB had already relicensed RocksDB following https://issues.apache.org/jira/browse/LEGAL-303
140.
by jjirsa 9y ago
https://issues.apache.org/jira/browse/CASSANDRA-13848 Created just for you
141.
by jjirsa 9y ago
Vice versa, if network is front and disk is back (as it is in the code).
142.
by jjirsa 9y ago
Using Cassandra as a key value store is ok, but ignores one is it's legit strengths.
143.
by jjirsa 9y ago
Datastax academy is probably the best free source Searching YouTube for Cassandra summit talks is probably second There was a push to do some better docs on the ASF website but it's just manpower that is currently spending time writing
144.
by jjirsa 9y ago
It's not you, it's the author. That's a horrible way to describe it. It's partitioned: Cassandra is a clustered database that will automatically route data to the right nodes. It does this by partitioning a token ring am
145.
by jjirsa 9y ago
It's not really that quick of a change - it's been in flight for something like 4 years? Maybe 5? And thrift is still supported until 4.0, so you can use the old style for quite some time.
146.
by jjirsa 9y ago
The clustering provides a ton of speed improvements if your data model can keep partition sizes small - especially if you use spinning disks, cassandras storage engine will make reading adjacent rows in a partition nearly free (especially w
147.
by jjirsa 9y ago
Use Cassandra when you need real time HA cross datacenter without having to manually fail over Use Cassandra when you're going to need to grow our database cluster often and don't have tooling to handle resharding Use Cassandra wh
148.
by jjirsa 9y ago
As a long time Cassandra user: people use sstable2json all the time, but most people don't have 100gb sstables (or 20gb sstables that make 100gb of json) Certainly something we can do better - how would you break it up? Adding a key to
149.
by jjirsa 9y ago
Cutting a check for 3-6 months severance as a sign of good faith, wrapped up in an NDA. There's no cause for anything more than that.
150.
by jjirsa 9y ago
It's not about virtue signaling, he was almost certain to be terminated just because it was a ridiculously stupid thing to say - you can't tell your teammates that they were hired because their employer lowered the bar and expect

More ›