[untog]

I've found it useful in storing and querying JSON documents. Basically, scraping an API (for me it was an OpenTripPlanner instance I had set up) and then being able to query any property in the data very easily.

But I didn't use joins, nor was this anywhere near a production server. From my understanding, if you have a heavy requirement for joins then you just shouldn't be using MongoDB in the first place. It isn't a traditional relational database.

[victormx]

I have come to the same conclusions, for that reason I asked this question, one of the reasons that i like mongodb is that data is in JSON

[indolering]

Yeah, 9/10 of the reason people use NoSQL is because it acts like an ObjectDB for JS. MariaDB does has this now as well: COLUMN_JSON(dyncol_blob);

https://mariadb.com/kb/en/column_json/

[neilk]

Postgres is getting there, with JSON columns. You can do hstore if you like key-value, or mix it with plain old SQL tables. This combination works well for me.

[glimcat]

I use Postgres HSTORE via Flask-SQLAlchemy. As far as my code knows, it's dict() all the way down.

And if I want to attach non-kv data like last_updated, or have foreign key relationships between one dict() and some other stuff like the corresponding user record's primary key - it's already in an RDB.