Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

So your take is, I should run two whole seperate databases so I can store my property tables in a k-v store instead of in a trivial table?


If it's more efficient? Hell yeah.

Also, say you end up with memcached, or redis, why not cache session data in it so you don't need to query the database or the fs, etc..

Usually there are a lot of things to put into a cache. And memory is always faster than disk.

But that's all assuming you really need it. I wouldn't throw anything new at an app when it's not necessary. You need to know that yourself.


The take is, just because you already have a database, it might not be the best place to but all your data.


In what way are my users going to notice that I stored a prop table in Redis instead of MySQL? Because I don't think they're going to notice ever, but I could be wrong.


Ouch.

They'll notice when your application is faster and more robust. You don't use a key-value store to impress your users.

Robustness can also lead to easier development, more features, better service, whatever.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: