3 ms·
I didn't say they were unreliable. I said they were eventually consistent. ACID is a wonderful model for lots of data problems, but wholly inappropriate for lot
by kstrauser 7y ago
I didn't say they were unreliable. I said they were eventually consistent. ACID is a wonderful model for lots of data problems, but wholly inappropriate for lots of things where availability matters more than perfect consistency before it's reconciliation time. For instance, suppose you're reading data from a million sensors in a particle collider. You absolutely don't want to model that as a million `BEGIN; INSERT INTO readings (sensor, value) VALUES ('particle_489285', 83); COMMIT;` queries. It's probably more appropriate to shard those sensors to N servers that log the readings to local journals in realtime, then upload them to a central data warehouse later after the experiment is finished. Reliability is extremely important there, but realtime ACID-style consistency would add nothing of value.
Financial transactions aren't the only "real" work out there, and there are lots of "fun" projects that are deadly serious.