SQL and NoSQL databases do the same thing in different ways. It is possible choose one option and switch to another later, but a little planning can save time and money. We'll try to suggest best suited from your project requirement.
What type of project you want?
Project require Multi-row transactional support?
Normalization or Denormalization ?
(Normalization minimizes data redundancy, there is no repetition for any unique thing for ex- publisher information for every book only the reference to it is stored)
Is your data growing at unpredictable rates?
Store Tabular data or Document data ?
Schema based or Schema less design (Schema based like we have all information relation)
Two or more updates can be executed in a transaction an all-or-nothing wrapper that guarantees success or failure?