How to evaluate your next database

Just use PostgreSQL and don&#x27;t evaluate anything. PostgreSQL can handle an enormous number of use cases, scales very well and can be made redundant with read-only nodes too.<p>If you outgrow PostgreSQL, you have an excellent problem and are probably making tons of money. Don&#x27;t waste mental power on this; just use it and focus on your business&#x2F;product&#x27;s core value proposition.<p>Or, read the article, which reaches the same conclusion with way more words. :)

I think the default should be some RDBMS. Unless you already know your domain - which is unlikely. Get to know your product, problem space, domain - then with more information you can start optimising by adding more specialised db engines (if this optimisation provides benefits of course).

PG 11 + Citus + cstore_fdw + PipelineDB is my preffered Database (OLAP + OLTP + Streaming middleware + HA) stack choice

TLDR: Database vendor for Postgres makes Postgres look good.<p>My startup uses Postgres though and we like it.

Postgre is also my go-to relational database.