STOP SCALING UP

- SOFTWARE SHOULD NOT SUPPOSED TO SCALE

- YEARS OF SCALING yet NO REAL WORLD USE FOUND for going higher than YOUR FAMILY

- Wanted to go higher anyway for a laugh? We had a tool for that: It was called "EVERYONE HAVING THEIR OWN SERVERS"

- "Yes please give me 5 instances of Redis. Please cluster my databases in Kubernetes Docker Container Pods" - Statements dreamed up by the utterly deranged

"Hello I would like to deploy 5 instances of my frontend please"

They have played us for absolute fools

you can tell i do not know how scaling works from the terrible examples in this joke

all i know is that if you do software with scaling up in mind it ends up terrible for my use cases and i will make jokes like this until you stop

@admicos Also, don't underestimate how far a single PostgreSQL or SQLite instance can scale *if you're querying it efficiently*. Throwing 100 parallel servers at something doesn't do jack if your main algorithm is O(2^n).

@tek @admicos this.

There is still something I don't understand about the fact that we seem to consistently have needed expensive racks of servers for the same CRUD apps in the past 30 years, even while said servers were getting about a gazillion times faster

@ssafar @admicos Well, because we need to make it highly available, of course! (Then we put it behind a load balancer, aka "single point of failure".)

Sign in to participate in the conversation
Mastodon

Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!