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

PostgreSQL

2158 readers
1 users here now

The world's most advanced open source relational database

Project
Events
Podcasts
Related Fediverse communities

founded 3 years ago
MODERATORS
Ategon@programming.dev
starman@programming.dev
jnovinger@programming.dev
1
Postgres is Too Good (And Why That's Actually a Problem) (dev.to)
submitted 1 year ago by cm0002@lemmy.world to c/postgresql@programming.dev
4 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[โ€“] Endmaker@ani.social 0 points 1 year ago* (last edited 1 year ago) (1 children)

TLDR

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

Postgres can do literally all of this.

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 0 points 1 year 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).