3 ms·
So, would you say that it's a solvable problem, but it's so time consuming or difficult that a traditional relational database is a more appropriate database fo
by gwbas1c 10y ago
So, would you say that it's a solvable problem, but it's so time consuming or difficult that a traditional relational database is a more appropriate database for average developers? (Remember, the Diaspora guys were right out of college and inexperienced.)
It's as if MongoDB is great for prototyping, and great for lossy data at scale, but it can't hit the middle.
- phamilton 10y agoMongo's problem isn't really the lack of schema or joins or anything. It's the mountain of false assumptions people make around its behavior. If you understand the limitations of the libraries and systems you use, you can solve most problems. The issue is that most people don't understand those limitations. Mongo gets an especially bad rap because it actively pushed misleading information as part of its sales pitch.