Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Friendly: NoSQL With MySQL in Ruby

jamesgolick.com

Post reply on HN
Print view View original

11–19 of 19 posts

Re: Friendly: NoSQL With MySQL in Ruby

#11

Post by eliot_10gen »

jamesgolick wrote: post #3
antirez wrote: post #2

Even if NoSQL solutions are new, there are no data durability concerns in my opinion. I can talk for Redis but my guess is that's the same for the other datastores. In Redis to have full durability enable append-only-file: it's a text-only file, you can check by hand what's written inside your database. In addition even while running in append only file mode, you can still ask Redis to "BGSAVE" (crete a copy of the d…

Actually, we do run redis in production, and it has been awesome for us. But, for this particular aspect of our application, we see about 20GB of data growth per week. So, an all-in-RAM db isn't really practical. Either way, durability wasn't the issue for us. Mongodb has no write concurrency. So, when it got so overloaded with data that queries were taking forever, we had no way to purge older data without blocking…

Or if you want to only keep x amount of data around - thats what capped collections were designed for.

Re: Friendly: NoSQL With MySQL in Ruby

#12

Post by hello00768 »

welcome to: http://www.wowowbiz.com/ The website wholesale for many kinds of fashion shoes, like the nike,jorda-n,prada,ad-idas, also including the jeans,shir-ts,bags,ha-t and the decorations. All the products are free shipping, and the the price is competitive, and also can accept the paypal payment.,after the payment, can ship within short time. http://www.wowowbiz.com/

Re: Friendly: NoSQL With MySQL in Ruby

#15

Post by apgwoz »

Tompy wrote: post #8

If only this was written in python... A port anyone?

Actually, friendly definitely "beat me to market", but I did start building this on top of sqlite3 a few weeks ago. My purpose was just for play--I was going to naively compare its performance to something like Tokyo Cabinet to see if matched at all. I can throw the code up somewhere, but it's neither complete, nor well thought out, merely a hack.

Re: Friendly: NoSQL With MySQL in Ruby

#16

Post by apgwoz »

dpritchett wrote: post #13
Tompy wrote: post #8

If only this was written in python... A port anyone?

FriendFeed's Tornado has a database.py on github, maybe it will get you started: http://github.com/facebook/tornado/tree/master/tornado/

database.py isn't really in the same realm, but it could certainly be modified and enhanced to support this abstraction.

Re: Friendly: NoSQL With MySQL in Ruby

#17

Post by mdirolf »

jamesgolick wrote: post #3
antirez wrote: post #2

Even if NoSQL solutions are new, there are no data durability concerns in my opinion. I can talk for Redis but my guess is that's the same for the other datastores. In Redis to have full durability enable append-only-file: it's a text-only file, you can check by hand what's written inside your database. In addition even while running in append only file mode, you can still ask Redis to "BGSAVE" (crete a copy of the d…

Actually, we do run redis in production, and it has been awesome for us. But, for this particular aspect of our application, we see about 20GB of data growth per week. So, an all-in-RAM db isn't really practical. Either way, durability wasn't the issue for us. Mongodb has no write concurrency. So, when it got so overloaded with data that queries were taking forever, we had no way to purge older data without blocking…

This is fixed now - large deletes won't block the world forever: http://jira.mongodb.org/browse/SERVER-494

Re: Friendly: NoSQL With MySQL in Ruby

#18

Post by jamesgolick »

mdirolf wrote: post #17
jamesgolick wrote: post #3

Earlier quoted context omitted.

Actually, we do run redis in production, and it has been awesome for us. But, for this particular aspect of our application, we see about 20GB of data growth per week. So, an all-in-RAM db isn't really practical. Either way, durability wasn't the issue for us. Mongodb has no write concurrency. So, when it got so overloaded with data that queries were taking forever, we had no way to purge older data without blocking…

This is fixed now - large deletes won't block the world forever: http://jira.mongodb.org/browse/SERVER-494

Awesome. You guys rock!
Post reply on HN