c# guy here. coming from a sql+entity framework background, the learning curve for mongodb was massive for me. but I'm never going back to that god-aweful tables+columns+rows nightmare again. my apps don't need an ORM layer anymore. thinking in objects/entities all the way down to the DB is a huge convenience. it's super fast for most use cases. the aggregation framework can run circles around sql queries imho. sharding/ replicating is easy enough. i developed my own library on top of the official mongo driver simplifying the API and adding some features such as migrations, fuzzy text search, gridfs alternative, easy relationships, etc. I've written a few articles about those here on DEV if anyone's interested.
c# guy here. coming from a sql+entity framework background, the learning curve for mongodb was massive for me. but I'm never going back to that god-aweful tables+columns+rows nightmare again. my apps don't need an ORM layer anymore. thinking in objects/entities all the way down to the DB is a huge convenience. it's super fast for most use cases. the aggregation framework can run circles around sql queries imho. sharding/ replicating is easy enough. i developed my own library on top of the official mongo driver simplifying the API and adding some features such as migrations, fuzzy text search, gridfs alternative, easy relationships, etc. I've written a few articles about those here on DEV if anyone's interested.
I'll have to take a look at those articles!