This document discusses considerations for choosing between a NOSQL or graph database model for a project. It outlines some disadvantages like choosing the right database and data model. Advantages include flexibility to handle unstructured data and different data modeling options. An example shows a basic schema for a social media application using a NOSQL document model with separate user and post collections. A graph model is suggested to avoid duplicate data by linking users and posts. Factors to consider like data size, write frequency, linking, aggregation and backup are also listed. Tables compare some popular NOSQL databases.