zlacker

>>eduard+(OP)
Not keen on your data store choice. Mongodb introduces a lot of other problems. The problem with schemas is an easier one to solve imo

>>chaost+qz
Fair point, although we didn't choose MongoDB just because of schema handling. We've been using MongoDB in production since 2013, so it was a natural choice since we already know a lot more about it than any other database.

For the problems you're mentioning, what we've seen is that many people use it incorrectly, and we're building the framework in a way that prevents that in the app layer. But still curious about your experience - what are the biggest problems you've had in production MongoDB?