>people actually use this in production
>>54974742
a long time ago computer scientists realized that some setups might offer an order of magnitude performance improvement at a cost of "not necessarily 100% recall". in lots of cases, that's an acceptable loss for the proposed gain.
the internet basically works on this premise - that you can take a negligible loss on consistency in exchange for a MASSIVE boost to performance. welcome to the internet of inconsistency.
>>54974742
People use PHP and Node.js in production too
blame it on the hipster web dev generation
>>54974780
The internet mostly runs on TCP, so no you dont take any loss.
Streaming and Online gaming on other hand work just throw data on the wall and dont give a fuck if it sticks or not.
>>54974890
TCP isn't webscale.
>>54974742
What is this?
>>54976944
MongoDB may not include in a query result one or more matching documents, if those documents are being updated at the time.
I consider this to be an extremely severe problem and absolutely fatal to any idea of using Mongo.
>>54977504
Then it doesn't fit your use case and you should be using an acid compliant database like PostgreSQL. You wouldn't use mongo to develop a financial app, this is fucking obvious.
>>54974780
stfu
