33 ms·
> I, well, one my companies, have been using mongo for a while without any problems. I cannot comment about is reliability but as a business tool, in the niche
by joepie91_ 11y ago
> I, well, one my companies, have been using mongo for a while without any problems. I cannot comment about is reliability but as a business tool, in the niche area we operate, it served us well.
The issues I listed provably exist. That you haven't run into them yet doesn't change that - and quite likely, you might not even know whether you've run into it.
Losing data or having your database open to the wide internet, for example, are two scenarios that you will likely not be aware of unless you explicitly test for them.
> I've got nothing against relation databases but there are not a solution to every single problem.
And if you'd read my post carefully, you would've seen that I make no such claim. They do solve many problems, however.
> Heck, why not decide first if you can use flat files?
Flat files are rarely the correct solution. Race conditions ahoy!
> Do you really need to query and join. Not all problems require that sort of thing.
Many do. And even if they don't, MongoDB is still not the right choice.
- foobarian 11y agoIf nothing else psql has a nice tabular output. Sometimes I go out of my way to import something into a local pg instance just so I can format things using psql.
- facetube 11y agoPostgres 9.4 even has `jsonb` and GIN indexes, which in a lot of ways provides nicer schemaless storage than some of the NoSQL databases provide. You're also free to mix in traditional relational tables (since `jsonb` is a data type like any other), or even efficiently join two tables based on a JSON containment operator. I haven't looked in to it _too_deeply, but what I've seen so far looks really neat.