Please answer the short prompt regarding database storage solutions and structure. Which data storage solution is best?

Question

Situation:

You've just been brought into a company that's looking at how decisions are ultimately made by a Hollywood studio regarding casting. You have been asked to collect and store a wide variety of data in order to better understand how and when various actors, directors, producers, and agents have worked together in the past. For example, it's worth noting things like when a collection of actors worked together on a three year TV project. Or, which agents have represented which actors over the years. While what you may uncover and what patterns may emerge is unclear, what's evident is that you need a way to record and delve into the complex relationships between people in a variety of situations.

What type of data storage solution would you recommend and why?

For simplicity's sake, please limit suggestions to the concepts of: 

Unstructured (or lightly structured) Data Lake Storage, Key-Value Store, Column Store, Document Store, Graph Database, Relational Database designed for OLTP, or Relational Database designed to serve as a Data Warehouse.

Answer 1

The situation describes a graph-like, linked data. Therefore, the best fit for these types of data structures are NoSQL Graph Databases (Neo4J, GraphDB, FlockDB, etc.). You can surely design a complex schema (ERD) using traditional RDBMS, linking all entities via many-to-many connectors, but queries for traversing graph databases would come more natural after the data is stored. You describe WHAT you want and not HOW you want it. Graph databases also have performance optimizations for handling these types of data and queries.