Is there a matrix of features or use case scenarios for the various NoSQL options out there? e.g. i have a lot of person data with various attributes like appl

Is there a matrix of features or use case scenarios for the various NoSQL options out there? e.g. i have a lot of person data with various attributes like applications, schedules, choices, demographics, courses, etc. (university). At certain times of the year, a lot of transactions would occur and at other times, it'll be getting very low traffic/transaction requests. MySQL tends to be a PITA if we try to modify certain things to add or remove tracking and so on while live hours and as things are run, unfortunately a lot of changes come in unplanned. How should I go about finding the best fit for this scenario?