One database for everything: the case against Redis, Mongo, and Pinecone (postgresisenough.dev)
The catalog is specific: UNLOGGED tables instead of Redis, SKIP LOCKED instead of a job queue, pgvector instead of Pinecone, PostGIS instead of your geo stack, with a rule that you may leave Postgres only after documenting why it wasn't enough.
A developer running an email CRM on Redis isn't buying the premise: it's trivial to set up and never crashes, so what difficulty is this genre even describing?
Sign in to save