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.
I'm partial to Postgres in general but the most important considerations are really your data model and other requirements, not what you're running. If your data model is hierarchical with few relationships (unusual, but it happens) MongoDB is built for that. If your project is small-scale enough that you're okay with the database living on the same filesystem and having only one active connection at a time, SQLite will do perfectly well, although if you've already got Postgres running there's no reason not to use that either.
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.
I'm partial to Postgres in general but the most important considerations are really your data model and other requirements, not what you're running. If your data model is hierarchical with few relationships (unusual, but it happens) MongoDB is built for that. If your project is small-scale enough that you're okay with the database living on the same filesystem and having only one active connection at a time, SQLite will do perfectly well, although if you've already got Postgres running there's no reason not to use that either.