Please enable JavaScript.

Coggle requires JavaScript to display documents.

Neo4j (modeling data for Neo4j (Graph modeling best practices (善用…

- - - - These are typically used to store entity information.
      - ex. there are the individual books, readers, and authors that are present in the library data model.
    - - These are used to connect nodes to one another explicitly
        and therefore provide a means of structuring your entities.
      - Relationships always have a type, a start- and an end-node, and a direction.
    - - Both nodes and relationships are containers for properties,
        which are effectively name/value pairs.
      - Just like a record in the relational database world has one or
        more fields or attributes, so can the node have one or more properties.
    - - Labels are a means to quickly and
        efficiently create subgraphs.
      - labels are primarily used for indexing and
        some limited schema constraints
  - - - 你要先想想你會針對資料問什麼問題，根據問題來設計你的 graph model
    - - 許多好的 graph database model 會使用多個 relationships 來建立 nodes 間的不同的 use case scenarios
      - 透過 relationships 來建構 use cases 時，記得要給予適合的命名，才能妥善表達 use cases
      - The general recommendation is to use as few generic names such as HAS_A or IS_PART_OF as possible, but to be more specific in these naming efforts.
    - - When we discover these types of relationships in a graph model, this typically means that there's an additional node to discover that we have split out a new entity.
    - - If we don't need to evaluate the alcohol percentage during the course of a graph traversal, we are probably better off keeping it as a property of the end node of the traversal.
      - If we need to evaluate the alcohol percentage of a particular (set of) beer brands during the course of our graph traversal, then splitting it off into its own node category is probably a good idea. Traversing through a node is often easier and faster than evaluating properties for each and every path.
    - - Knowing what the questions you want to ask of the data are will massively impact its design model, and chances are that you will need and want to iterate over that model multiple times to get it to a stable state
  - - - 應該這些屬性拆成多個 nodes，透過 relationships 建立連結
    - - 建議將多個 concepts 拆成多個 nodes，擁有各自的特性與屬性
    - - 沒有建立 relationships 的 nodes，就無法有效利用 graph database 的優點，就不需建立此 nodes
    - - Supernodes can be a real issue in graph database models and should be avoided when setting up your Neo4j instances.