this post was submitted on 15 Jun 2025
43 points (100.0% liked)

PostgreSQL

1572 readers
1 users here now

The world's most advanced open source relational database

Project
Events
Podcasts
Related Fediverse communities

founded 2 years ago
MODERATORS
Ategon@programming.dev
starman@programming.dev
jnovinger@programming.dev
43
Postgres is Too Good (And Why That's Actually a Problem) (dev.to)
submitted 6 months ago by cm0002@lemmy.world to c/postgresql@programming.dev
4 comments fedilink hide all child comments
top 4 comments
sorted by: hot top controversial new old
[–] Endmaker@ani.social 18 points 6 months ago* (last edited 6 months ago) (1 children)

TLDR

Redis for caching, RabbitMQ for queues, Elasticsearch for search, and MongoDB for... reasons?

Postgres might be too good for its own good. It's so capable that it makes most other databases seem unnecessary for 90% of applications.

Thanks for sharing. The built-in text search sounds helpful for the project I'm working on.

[–] jubilationtcornpone@sh.itjust.works 8 points 6 months ago

The full text search works quite well. Also, if you just HAVE to store a bunch of data in JSON, it will do that too as well as index and query it. No need for MongoDB (which is the wrong tool for the job 99% of the time anyways).

[–] zr0@lemmy.dbzer0.com 1 points 6 months ago

laughs in ClickHouse

[–] veer66@social.vivaldi.net 1 points 6 months ago

@cm0002 I'm using PostgreSQL's JSON queries, full-text search, and pattern search with n-gram index.