Designing a data warehouse based on NoSQL?

Question

NoSQL

As the use of NoSQL expands, many questions arise.
There is an RDBMS, and for designing storages it has Entity-Relation and relational logic, there is the concept of normal forms, and vice versa, denormalization, and criteria for its use. There is SQL that allows you to run queries.
And what about NoSQL? Is there a theory, best-practices etc? How to learn?

Answer 1

NoSQL gives you the ability to extract as much information about an object as possible with a single request. This, as far as I can tell from my little over a year of experience, is the underlying concept.
Of course, this inevitably leads to widespread smearing and copying of information, but it’s really nice to pull out the content of an article with comments in one request (a standard example from the documentation)

Answer 2

NoSQL is too broad a concept, and the various NoSQL DBMSs are too different to speak of universal best-practices.
If models need to be stored as simple blobs without particularly complex inter-object relationships, Riak can be convenient for a soft-realtime system.