3 ms·
MongoDB was never about its benchmarking, scaling or sharding abilities. It was about two things: #1: No schema. If you're prototyping, schemas just slow you d
by dkyc 12y ago
MongoDB was never about its benchmarking, scaling or sharding abilities. It was about two things:
#1: No schema. If you're prototyping, schemas just slow you down. Maybe that changes as your application matures.
#2: Great drivers. The amount of pain to get a basic CRUD app running with a SQL backend is just too high: push the data from the browser to the server in JSON or XML, validate, convert into database schema, sanitize using prepared statements or stored procedures, and send it off. Compare that with MongoDB: it's just JSON™.
The one thing that killed MongoDB was lack of reliability. Even when you're a startup, you may not lose data. I think MongoDB could have easily dropped 50% of performance & scalability for data security and it would be well off now. It was never intended to be the safe, sane choice for big enterprises.