kkovacs

Seems like an interesting project too, will try it! Thanks!

Thanks, Gordon, I put it in (shortened some lines).

It would be great to have a "more general" for-example, since noone outside Facebook meets the problem of "let's build Facebook's messaging database" :) Any suggestions?

Good point, and it's not there since I only wanted to speak from experience; especially with rumors of Cassandra scaling problems at Reddit and Digg.

But sure thing, "infinite" scaling is probably best done with the Dynamo-like stuff like Cassandra and/or RIAK.

Only beacuse I don't know HBase very well. I'll read up on it, at least try it, and then add that too (and also maybe Tokyo Cabinet).

Thanks for the feedback!

THAT jchrisa, seriously? Wow, I'm honored that you chimed in! Thanks, man :)

I didn't mention that (it does not really matter when choosing one right now), but I too consider that one of the most exciting explorations in this area!

Keep up the good work!

Thanks, I appreciate the kind words!

K.

No conspiracy behind the 15 years :) I estimate that that's about the time SQL bot really mainstream (as opposed to dBase files, etc).

I'm old enough to remember somebody being threatened with firing for using SQL, because of it's bad performance compared with seeking. :)

I agree with that, but you know, it's very hard to find good examples. :) I'm open to better suggestions :)

I agree, ultimately it comes to everyone's own definition of "tyranny". :) I meant it as "not really having any defensible other choice". (While, of course for example CDB and BerkleyDB have "always" existed.)

I think nobody expects SQL's "market share" to fall to low levels, especially with noSQL requiring much deeper understanding of the data and it's planned use. NoSQL practically operates on a lower layer than SQL does.

Still, it's nice to see people thinking about data storage choices and not going blindly to MySQL/Oracle/etc!

Wow, thanks, very nice example! (And also thanks for expanding my fruit knowledge :) )

Thanks Sean, I'll read up on that. I have experience with CouchDB only under normal loads -- our heavy-load stuff (stock data) uses Redis. :)

Thanks, amended RIAK with Erlang map/reduce and full-text search! (I need to read up on Protocol Buffers, but it sounds useful, too).

(Updated: typo)

Protocols: great idea, thanks man, amended it!

Blazing fast: I mean compared to the other four.

Perhaps it is. I still hope that it's useful :)

Not that they get thrown away, they are still very useful. But at least there's an alternative now.

I mean, seriously, Zabbix keeping monitoring data in MySQL? Also Piwik? That's a sick solution, IMHO. :)

(BTW, I love Zabbix and Piwik. Use them both. Only I think that having no good alternate data store at the time of their writing, their data storage is suboptimal.)

I meant database consistency in the sense of never needing "repair tables"; although as far as I know, CouchDB's automatic conflict resolution is also consistent (based on UUIDs), isn't it?

Clarified it, thanks!

Yes, if versioning is the main point, then surely one should take special measures to keep them, as in the case of invoices (stornoed, stornos stornoed, etc). As for a CMS system, for example, it's nice to have most of the history, but nobody gets hurt if some gets lost during replication outages, etc.

Just my $0.02 :)

K.

I don't know that one yet, but I promise I'll read up on it! Thanks!

K.

Both of these are good ideas, I like them!

Of course one tries to do that, that's exactly what the question is aimed at. :) How could education happen but through their own understanding?

It's easy when one is already at the meeting when such things are to be discussed. But what often happens in real life, is that a sales guy (an intermediary!) comes, and asks, "hey I have this client, he needs this and this, can you guys give a quote by tomorrow?" :)

Don't tell me such a thing never happened in your praxis. :)

Yes it is. But that would be a pretty long headline, doesn't it? :o)

Point taken :)

My .vim/GetLatest/GetLatestVimScripts.dat:

ScriptID SourceID Filename

--------------------------

642 1 :AutoInstall: getscript.vim

1075 1 :AutoInstall: netrw.vim

1502 1 :AutoInstall: vimball.vim

2010 1 :AutoInstall: sessionman.vim

1896 1 :AutoInstall: ragtag.zip

273 1 :AutoInstall: taglist.vim

1984 1 :AutoInstall: vim-fuzzyfinder.zip