All geek questions in one place

What data modeling tools are used by nosql (couchdb) developers?

At some point, I assume that any developer for couchdb (or another nosql option) should still determine what should be stored in each document. And it seems that, although very rare, from time to time we need to have some relationship between these documents.

So, do people still use ER-type software (like Workbench) to create a visual representation of data stored in different documents? Is anyone working on developing nosql specific methods for identifying data that needs to be captured?

We are now using the list of markers on the wiki pages, any suggestion for something better?

+4
source share
2 answers

I do not expect such tools to appear for a while, especially considering that CouchDB released 1.0 just a few months ago, and there are still a lot of changes in the project. In addition, such tools should be maintained until real best practices appear, but this can only happen after many years of real experience.

Although there are other reasons for this, relational databases simply have not had graphical tools for years, if not decades. I cannot imagine that new database systems like these will evolve much faster.

+1
source

I would use a class diagram:

  • replace each association with a composition or aggregation,
  • See which classes should be read (in general) and modified,
  • add simple attributes (strings or int).

With this diagram, you have design tips:

  • for detailing documents,
  • URL patterns
  • "JSON Schemas".
+1
source

Source: https://habr.com/ru/post/1344243/

More articles:


All Articles