Geek Answers Handbook

Is RavenDB really suitable for this concept?

Firstly, a caveat: I'm pretty new to document database concepts, so this may be a very obvious question.

I need to develop a system that supports a deep hierarchical catalog of the parts that make up very complex products. It will describe in detail the physical components that make up each part, and each part can be components of other parts - up to the final product. Like this:

Widget
 |- Sprocket
 |  |- A4 nut
 |  |- B15 screw
 |  |- Sprocket Backshell
 |- Flange
 |  |- A4 washer
 |  |- Flange Housing
 |- Widget Assembly

The widget in this example can then be included as part of another product.

Each product can contain from tens of thousands to hundreds of thousands of parts, and each type of component has different, unrelated properties that must be maintained. These properties may include compounds between related parts.

, SQL Server, 120 . 85% . - - .

- , . , , , .

RavenDB , , , , . , - .

RavenDB ? , ?

+5
2

, , .

RavenDB , , , :

  • ?
  • , ?
  • ?
  • , /?
  • .
+5

:

Part
  - PartId
  - Name
  - ...more fields..

PartRelations
  - ParentPartId (PK)
  - ChildPartId (PK)

, , , .

, .

PartAttribute
   - PartId
   - Attribute
   - Value

, .

Attribute
   - AttributeId
   - AttributeName
   - ..datatype?.. (for pretty formatting logic or other..)

PartAttribute AttributeId, Attribute. , , , ,

, , , , , , .

+3

More articles:


All Articles