It's pronounced Diane. I do data architecture, operations, and backend development. In my spare time I maintain Massive.js, a data mapper for Node.js and PostgreSQL.
Databases are designed to handle "a lot of requests". Your data model is the most important determinant of what database to use, not your throughput, and if you don't have any reasons not to stick with a relational database, the answer is probably Postgres. If your needs diverge from the relational model, this is a good starting point for your research into NoSQL offerings.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Databases are designed to handle "a lot of requests". Your data model is the most important determinant of what database to use, not your throughput, and if you don't have any reasons not to stick with a relational database, the answer is probably Postgres. If your needs diverge from the relational model, this is a good starting point for your research into NoSQL offerings.