4 ms·
That's pretty much what I said. Conversely, you can't vertically scale a database (beyond throwing ever more CPUs, RAM, and RAIDed SSDs) without severe tradeoff
by kstrauser 7y ago
That's pretty much what I said. Conversely, you can't vertically scale a database (beyond throwing ever more CPUs, RAM, and RAIDed SSDs) without severe tradeoffs in electric bills and support contracts, and while still not getting the advantages of geographic redundancy. For instance, notice that none of the FAANGs are serving their websites off mainframes. Cost-per-server isn't the only reason for that.
My point wasn't that mainframes aren't useful - they are! - but that they're not good solutions for a lot of the new problems people are trying to solve lately. For instance, a huge portion of fun challenges are perfectly fine with eventually consistent solutions that optimize for availability, where one single piece of reliable hardware behind a couple of redundant peering connections simply can't compete with 1,000 reasonably reliable nodes distributed globally.
- zozbot234 7y ago> For instance, notice that none of the FAANGs are serving their websites off mainframes Obviously, nobody cares if the data that makes up your FB/Twitter timeline or Google search results page is less than completely reliable. The new problems people are trying to solve with horizontal scaling and distributed computing may well be "fun" for users and developers alike, but fun is quite different from generally worthwhile.
- kstrauser 7y agoI 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.
- estebarb 7y agoAltavista started in a DEC mainframe. Google architecture (and Amazon) was forced because a powerful constrain: some time ago they didn't have enough money.
- kstrauser 7y agoGiven the size of the web back then, running Altavista on a mainframe made sense. But how many exabytes can you stuff into any small collection of units today if you wanted to? Even today, reading the specs for the unit mentioned in the linked article, I’d have a hard time imagining running the Amazon.com website off a single mainframe. The shopping cart? Sure. The funny matching like “pjama wih ft” showing me “pajamas with feet”? I’d hate to be the one who had to power a million of those per second.