|
![](/i/fill.gif) |
http://groups.google.com/group/HAppS/browse_thread/thread/8663c04f3b104133
"Happstack scales, SQL fails!"
Um, yes, that's right. Some toy application that somebody wrote in their
lunch break really is more performant than the likes of Oracle,
Postgress, DB2 or SQL Server. Sounds completely plausible to me... Oh,
wait. No it doesn't! :-P
I guess if you can afford to pay for 30 TB of RAM and you don't mind
living with the absolute certainly that some day you *will* lose all
your data and have no way of getting in back, then storing everything in
RAM is perfectly OK. But it must surely be a vanishingly small number of
scenarios where you have terabytes of data but you don't mind losing it all.
I especially love the subversive suggestion that data integrity is some
optional feature that's nice to have but not really "necessary". As if
you can somehow do without it. People whine about "it's too slow" as if
it's just overhead that you somehow don't really "need".
Given the choice between a slow program that gives me the right answer,
and some program that's much faster because it just spits gibberish at
you and doesn't bother checking whether it even remotely makes sense, I
know which one I'd choose. But maybe that's just me? :-P
Post a reply to this message
|
![](/i/fill.gif) |