Q:

Choose noSQL for a big security project - a lot or write, some read

I need some help choosing a noSQL for a security project that collects a lot of data.
It suppose to write to the noSQL a lot of data from many users, we will need to aggregate it, and we need to be able to fetch the data with sorting capabilities (for example: get some reports for top  50 users...) .
That means we have a lot of data inserts (no update) and sometimes read.
I saw a lot of noSQLs and I couldn't find one answer.
Thank you for your help.

A:

Mongodb is the most fashionable noSQL DB nowadays. This means great tools and makes easier to find skilled advice. It supports all the features I think you would need (sharding, Map/Reduce, noSQL):

project that collects a lot of data

Eventually you'll need to distribute your data amongst different machines and mongo has sharding for that.

we will need to aggregate it

You'll greatly profit from map/reduce for that

we need to be able to fetch the data with sorting capabilities

noSQL takes care of that

