People often say SQL has no problem to scale but they've never actually done it
People often say SQL has no problem to scale but they've never actually done it
20 comments
-
So there was this QA tester filling a million documents in the database (NOSQL) and then using a single fetch to get all the data without pagination and then telling me my library was first being slow and then crashing.
Of course I didn't handle
std::bad_alloc
-
Oh, he's on AWS, that might explain some things
-
How about adding indexes and stats on the appropriate columns, and have look at your execution plan while you're complaining. Bushels of low hanging fruit are ready to be picked for devs who bother with a little SQL performance tuning.
-
But that's work! How dare you ask me to do work!
-
-
😅 what year is this guy living in? SQL has scaled, probably better than any other software paradigm.
-
Yes, but if I do 80 joins and don't specify join conditions, things get, like, super slow, Scoobs!
-
That's why you should only left outer inner right join with a recursive select!
-
-
-
This guy is vibe coding his queries. That's the future of programming :(
-
God I hate that term. They just put vibe in front of it and act like copy/pasting things you don't understand is "coding."
-
-
Somebody needs to learn to design his database layout by common queries and performance standards.
-
Y’all must be running Oracle DB if your SQL is not scaling.
-
Do we need to bring out the Mongo DB web scale video again?
-
First thing I thought of when I read this, and if you click through to the actual Linkedin post, that's exactly what the twit is saying.
-
What is it about?
-
-
as someone who has never coded in SQL and only knows some python, SQL is so scalable it sheds every 3 weeks
20 comments