PostgreSQL

Pros

• Longhorn for storage, postgres and redis operator to make it insanely easily to rollout DBs.
• Parent context: I decided to go with uuid because it's supported by postgres. Reply: I decided to go with uuid because it's supported by postgres. I prefer db handle it's own primary key generation rather than relying on application level.
• The "Fetch IDs + Fisher-Yates" strategy decouples the logic of randomisation for which Node can be good at, from the storage of data of which Postgres is good at.
• If you're using Postgres for your data already, consider Postgres's full-text search feature. ... If you're doing something like searching a list of users by name/username/email, this is a decent way to do so without the overhead of a se...
• Other databases probably support GIN, but postgres definitely does.

Cons

• MySql/Maria, Postgres, etc. backing up the actual files is "practically" useless. You need to do a mysql_dump/pg_dump which generates a text file of sql statements, so you simply run it to restore.
• Well postgres can work aswell ofc, myself never tried it tbh i use either Mysql/mariadb or nosql/mongo for all of my projects, this was just my suggestion based on my experience
• Currently, I'm using postgres to save these, but I'm considering to moving into a OLAP db like clickhouse.
• I'm using Express and Postgres as backend in my case
• Storing sessions in Postgres works but isn’t ideal for performance or scalability.