4

I am trying to learn NoSQL, and am implementing that in a project I am working on now as a means to pick it up. I understand there are no hard rules around it. But I'd be happy to read on some of the following:

  • Guidelines on how to structure a NoSQL document.
  • Moving from a RDBMS to a NoSQL thinking.
  • Difference between storing data in a NoSQL to that from RDBMS

Thanks!

I do have previous experience in RDBMS, and have been working with them for years.

nubela
  • 1
  • 24
  • 75
  • 123

1 Answers1

1

Every concept will require to learn new thinking. Your question is to general for a specific answer.

You will structure and work with CouchDB documents in another way as with MongoDB documents. In CouchDB you will do queries with MapReduce. In MongoDB you have a flexible query interface similar to a RDBMS.

A Key-Value store requires a completely new way of thinking. You have to know your query patterns before you are able to structure your content the right way. You have no index, so you have to build your own structure.

One blog that gives a lot of NoSql information is http://nosql.mypopescu.com

Update

The Riak people have some interresting questions too:

  • Will my access pattern be read-heavy, write-heavy, or balanced?
  • Which datasets churn the most? Which ones require more sophisticated conflict resolution?
  • How will I find this particular type of data? Which method is most efficient?
  • How independent/interrelated is this type of data with this other type of data? Do they belong together?
  • How much will I need to do online queries on this data? How quickly do I need them to return results?
hellectronic
  • 1,390
  • 11
  • 15