DEV Community

loading...

Discussion on: PostgreSQL vs MongoDB

Collapse
chiefnoah profile image
Noah Pederson

I would consider graph databases their own thing, separate from traditional document (non-relational) and relational stores. But only very specific types of data fit properly into a graph database (GIS data, for example). If you're choosing between a document store and a relational store, there's a clear winner, which is the point I'm trying to make.

Also you are incorrect in saying that relational DBs don't support embedded objects, PostgreSQL does support embedded objects, either in the form of K/V, JSON (natively supported), and BLOBs. At least in the case of JSON, you can index on the objects too.

Thread Thread
greenroommate profile image
Haris Secic

Not read properly. They didn't, they do now and it makes no sense to store data in it which might varry in structure just becuse they did some support for it. Why use C for web API? Or even Rust. I don't care if I can it's much easier with others. Same goes for DB. Each DB has some purpose and forcing one type doesn't cut it for me. There's no clear winner. Just improper usage. You wanna store site clicks, and search requests body? Why the hell would I bother with structure, I just need it to push data so someone plugs a tool in it and do they're casual analitics which they probably delete on monthly basis or so.

Forem Open with the Forem app