I do use postgres but only as an rdb provider. I thought while it supports json data as a type, does it provide for all of the other advantages of nosql databases for their use case?

Ultimately I feel like the best solution is to have a single database provider that could do both fully. I'm not sure it's really there yet. But halpt to be told I'm wrong. I've not really needed that myself for my projects.

[–] jubilationtcornpone@sh.itjust.works 3 points 4 days ago

The query speed isn't quite there but I would say it's close enough for a lot of purposes, especially with proper indexing. And JSON column fields are indexable. Two things I've used Postgres' JSON functionality for are:

1.) Storing unstructured data. 2.) Storing structured data that would exceed the table column limit.

In both cases, I've typically needed to extract the relevant data from the JSON records to either be stored in another table of turned into a materialized view so live query performance on the JSON columns was not that important.

[–] gaybriel_fr_br@jlai.lu 0 points 4 days ago

Fair enough! Thanks for the detailed write-up