4 ms·
MongoDB is awful for development. I once started consulting on a Rails app project which used MongoDB. But I was never able to get productive: I had my develop
by dogweather 11y ago
MongoDB is awful for development.
I once started consulting on a Rails app project which used MongoDB. But I was never able to get productive: I had my development environment all set up, but then the code wouldn't work with the development database. I pinged the other dev:
"Oh, I made changes to the data model. I'll zip up and email you a new copy of the dev database."
This continued for a couple of iterations and I had to quit the project because I could never continuously get work done.
- berntb 11y agoI'm ambivalent to MongoDB, because I think that too often you'll find out later that you really, really need joins for something anyway. But your painful problems seems more like a problem with communication/documentation practices. DB changes will occur with SQL databases. It is about equally important to communicate them to other users of the DB. (But OK, it is easier to find the changes with an SQL DB.) (Yeah, I'm hellbanned.)
- CmonDev 11y agoI thought it cannot get worse than dynamic languages, but then they invented document databases.