Work Packages entity: Relational vs NoSQL Database Design? Should it reference itself?

This database holds assembly instructions data for shipbuilding, later used in a Augmented Reality Android application. The application asks the server (Node.JS) for the necessary files. Work Packages contain several Parts that must be mounted, each of these parts has the Files necessary needed by the application. Some Work Packages depend on another (eg. Work Package B1). They have a mount order, and it is possible to assign a worker to an individual work package, or see if the worker has the qualifications to mount the work package, by using a Type attribute. Relational Database Implementation: NoSQL Database Implementation: Workers { "username": "worker1", "password": "pass1", "type": ["electrical", "general"] }, { "username": "worker2", "password": "pass2", "type": ["pipes", "general", "welding"] } Work Packages { "id": 2, "Name": "2" "MountOrder": 2, "PackageDependecies": , }, { "id": 1, "Name": "1" "MountOrder": 1, "Type": "Electrical", "Worker:" ["worker1"] "Parts": [ { "Name:" "part1", "Files": [ { "Type": "obj", "File": BLOB.obj }, { "Type": "stl", "File": BLOB.stl } ] }, { "Name:" "part2", "Files": [ { "Type": "obj", "File": BLOB.obj }, { "Type": "stl", "File": BLOB.stl } ] } ] } Why is one implementation the best? Why should or shouldn't a Work Package reference the above Work Packages? There will be substantial reads but considerably fewer writes.