Just use sqlite until you can’t.
Then use Postgres until you can’t.
It's 2026, Just Use Postgres
111–120 of 349 posts
Re: It's 2026, Just Use Postgres
#112fair points made but I use sqlite for many things because sometimes you just need a tent
Re: It's 2026, Just Use Postgres
#113Caching is mentioned in the article: What do you guys feel about using PostgreSQL for caching instead of Redis? Redis is many times faster, so much that it doesn't seem comparable to me. A lot of data you can get away with just caching in-mem on each node, but when you have many nodes there are valid cases where you really want that distributed cache.
If you want to compare Redis and PostgreSQL as a cache, be sure to measure an unlogged table, as suggested in the article. Much of the slowness of PostgreSQL is to ensure durability and consistency after a crash. If that isn't a concern, disable it. Unlogged tables are automatically truncated after a crash.
Re: It's 2026, Just Use Postgres
#114No thanks. In 2026 I want HA and replication out of the box without the insanity.
You exceeded the step of maxing out the best server you can buy?
HA is not about exceeding the limits of a server. Its about still serving traffic when that best server I bought goes offline (or has failed memory chip, or a disk or... ).
Re: It's 2026, Just Use Postgres
#115Re: It's 2026, Just Use Postgres
#116Oh wow, the "Postgres for Developers, Devices, and Agents" company wants us to use Postgres?
Re: It's 2026, Just Use Postgres
#117Blog posts, like academic papers, should have to divulge how AI has been used to write them.
People used to write Medium/Linkedin slop by hand and they didn't have to disclose it. Slopping is its own punishment.
Re: It's 2026, Just Use Postgres
#118I find myself needing to start something quickly with a bit of login and data/user management.
Postgres won as the starting point again thanks to Supabase.
Re: It's 2026, Just Use Postgres
#119Earlier quoted context omitted.
The point is really that you can only evaluate which of alternatives is better once you have working product with data big enough - else it's just basically following trends and hoping your barely informed decision won't be wrong.
Agree to disagree here. I see a world where developers need to think about (reasonable) scale from day one, or at least very early. We’ve been seeing this play out at ClickHouse - the need for purpose-built OLAP is reducing from years to months. Also integration with ClickHouse is few weeks of effort for potentially significantly faster performance for analytics.
[flagged]
Re: It's 2026, Just Use Postgres
#120Oh wow, the "Postgres for Developers, Devices, and Agents" company wants us to use Postgres?
Postgres has its merits without the company who's also enjoying using it.