Like a simple blog database, how should NoSQL be designed?

  mongodb, question

Looking at NoSQL these days, I still don’t quite understand the conversion from tables, rows and columns in traditional relational databases to NoSQL.

For example, the simplest blog database design has a classification table, an article table and n articles for each classification.

How does this traditional relational database design change to Mongodb and Redis?

After using Mongodb, I designed it this way. For the article:

  • Title
  • Release time
  • Classification
  • Tags (using array types)

Through tag and classified query articles, aggregated Map/Reduce, etc. can be used.

For Redis, handling these is mainly implemented in their own applications.