6 ms·

I agree with you! And on that note I would like to see more articles that describe problems that NoSQL stuff is good at. This is probably the main reason why th

by CWIZO 17y ago

I agree with you! And on that note I would like to see more articles that describe problems that NoSQL stuff is good at. This is probably the main reason why there is so much confusion. Everybody is talking about how great cassandra/mongodb/couchdb/... is, but nobody tells you where and how to actually use it.

drhodes 17y ago
What I'd like to see are articles that discuss design techniques. Like, how to incrementally develop a key store db without inconsistencies? There's no schema so .. I'm worried about partial records after adding values to the non-schema. First these addresses didn't have a zipcode field, but now they do. What about relationships between records, isn't there going to be redundant data? What if the user changes their email in the account record, do I have to manually update their contact record? This is what foreign keys are for. OMG, Where am I ... Where's the exit? We're all gonna die! That's basically what I go through every time I think about it. It's a big scary fully loaded gnarly nested hash table aimed directly at my foot.
- CWIZO 17y ago
  That's exactly how I feel, and so far I haven't read a single thing that would clear this things up for me. And I read pretty much everything about this topic that I get my hands on. I'm really egger to learn this stuff, to know where to use it, so I could use it in my projects where appropriate. Somebody who truly gets NoSQL and has use it, should really really write something on this subject.
Nelson69 17y ago
Yes! That's the same stuff I've been smelling. I look at stuff like documents Google has published and Hadoop and I do think to myself that map-reduce and some of the massively distributed stuff could potentially teach RDBMs some new tricks. Then I see these articles and they're all about someone converting a blog from MySQL to MongoDB. I'd love to see the technical details of how Digg used MySQL, why it was slow and why NoSQL is better, how they use it. The more of this I see and the less real information the more I think they didn't know what they were doing in the first place.

by CWIZO 17y ago

drhodes 17y ago

What I'd like to see are articles that discuss design techniques. Like, how to incrementally develop a key store db without inconsistencies? There's no schema so .. I'm worried about partial records after adding values to the non-schema. First these addresses didn't have a zipcode field, but now they do. What about relationships between records, isn't there going to be redundant data? What if the user changes their email in the account record, do I have to manually update their contact record? This is what foreign keys are for. OMG, Where am I ... Where's the exit? We're all gonna die! That's basically what I go through every time I think about it. It's a big scary fully loaded gnarly nested hash table aimed directly at my foot.

CWIZO 17y ago
That's exactly how I feel, and so far I haven't read a single thing that would clear this things up for me. And I read pretty much everything about this topic that I get my hands on. I'm really egger to learn this stuff, to know where to use it, so I could use it in my projects where appropriate. Somebody who truly gets NoSQL and has use it, should really really write something on this subject.

Nelson69 17y ago

Yes! That's the same stuff I've been smelling. I look at stuff like documents Google has published and Hadoop and I do think to myself that map-reduce and some of the massively distributed stuff could potentially teach RDBMs some new tricks. Then I see these articles and they're all about someone converting a blog from MySQL to MongoDB. I'd love to see the technical details of how Digg used MySQL, why it was slow and why NoSQL is better, how they use it. The more of this I see and the less real information the more I think they didn't know what they were doing in the first place.