|
|
|
|
|
by rgo
4434 days ago
|
|
Our enterprise on-premise software package runs on Mongo, before it used to run on relational dbmses. Here's why we changed: - flexible document schema reduces migration complexity greatly, really important when we have our software deployed on many customers sites.
- flexible schema is also important to our product because we support custom forms and fields.
- the ability to store and search nested data
- replication is easy to setup
- easy to maintain, good export formats
- no dependence on customer's DBAs
- no more frustrating explain-plan debugging of underperformant joins
- text search (simple yet useful)
- regex support
- fast, up to 3x faster than SQL based engines for our use cases.
- works well as a cache
- decent also as a work queue with tailable capped collections. Our biggest complain: the lack of transactions combined with data denormalization pitfalls is a PITA to work around in code. Overall just a great db for when you need a flexible schema. |
|