3 ms·
"So there it is. SQL doesn't scale (effectively or efficiently)" I think you just re-iterated the author's reason for writing perfectly. Instead of saying 'SQ
by wavesplash 17y ago
"So there it is. SQL doesn't scale (effectively or efficiently)"
I think you just re-iterated the author's reason for writing perfectly.
Instead of saying 'SQL' (the query language) doesn't scale, perhaps you can say full ACID doesn't scale cheaply.
We spent a bunch of time looking at large scale distribution at Berkeley for the Mariposa project. The short version: if you want to break ACID then you have to take the semantics of the data into consideration. Transactional financial data needs full ACID, many other types of data have looser needs (status updates, etc) and those looser needs can be taken advantage of.
As it turns out, even common DB's like Oracle, Postgres and MySQL can be used differently to get much cheaper scale for certain types of data. See the FriendFeed article on MySQL as a docdb (also the Friendly ruby mapping on github).
To paraphrase the author:
"ACID scales just fine if you need it (and if you need it you most likely have budget for it). If you don't need full ACID, there are plenty of other cost effective solutions you can run on low bandwidth disks/memory limited CPUs. Mix and match to fit your needs.
Please, enough with the religion."
- rbranson 17y agoYou're arguing semantics. NoSQL = No"ACID-Compliant Relational Database with Normalized Table Design"
- joe_the_user 17y agoUh, that is a bit of a leap... It seems like every NEXT BIG THING comes in two parts. 1) The provocation: "Throw away design and do everything with testing" - "never use SQL again, just key-values" "Objects are Worthless!" 2) The sensible fall-back position you can use when challenged "Test are useful" - "You might not need full ACID", "We can benefit from shorter inheritance trees"... I suppose every new idea needs a way to make a splash...
- voidpointer 17y agoThis is what as the triad of thesis, antithesis and synthesis. A lot of progress works this way. [http://en.wikipedia.org/wiki/Thesis,_antithesis,_synthesis http://en.wikipedia.org/wiki/Thesis,_antithesis,_synthesis] Thesis (established view): SQL/ACID solves all you data problems Antithesis: Nobody needs SQL/ACID, let's throw it all out Synthesis: By carefully considering data integrity constraints we can find a more optimal data management solution for a particular problem (alternatively: let's go to the pub!)
- Groxx 17y agoExcellent plan. Alcohol always helps people get over arguments. Bones heal faster than internet battles :)