Horizontal Scaling of SQL Databases?
still_sick writes "I'm currently responsible for operations at a software-as-a-service startup, and we're increasingly hitting limitations in what we can do with relational databases. We've been looking at various NoSQL stores and I've been following Adrian Cockcroft's blog at Netflix which compares the various options. I was intrigued by the most recent entry, about Translattice, which purports to provide many of the same scaling advantages for SQL databases. Is this even possible given the CAP theorem? Is anyone using a system like this in production?"
Just store everything in a big XML file.
Agreed, we have massive sites serving millions of requests a day using Open Source relational databases and yet it seems everyone wants to use NoSQL because it's the hip new thing.
Naturally I start thinking of this: http://xtranormal.com/watch/6995033
MySpace is also slower than maple syrup in January.
Peter predicted that you would "deliberately forget" creation 2000 years ago...
I just select * from * and then sort it out with grep and cut.
"You should always go to other people's funerals; otherwise, they won't come to yours." -- Yogi Berra
Is to write better queries, I mean how hard can it be:
select * from (select * from A,B,C,D,E,F,G WHERE A.ID=B.AID(+) AND B.ID=C.BID(+) AND C.ID=D.CID(+) AND D.ID=E.DID(+) AND E.ID=F.EID(+) AND F.ID=G.FID(+) order by F.name ASC) where F.name='zzzzz'
Everything will work out, I swear.
Bye!
Congratulations, you just won Slashdot's buzzword bingo, please collect your prize at the cashier window in the back of the hall.
You really need to define your problem with much greater specificity to get a valuable answer.
The real problem is he lied on his resume, has no idea what he's really talking about, and now they're asking about it at his job...
Would you have preferred I have said bazillions?