News for hackers. Stuff that matters.
Re:How to make MongoDB not suck for analytics by AznHisoka on Sunday July 01, 2018 @09:00PM (#17438651)
"they can just copy the data into a different database that fits their needs."

That's easier said than done when your database is over 10 TB big.

Re:How to make MongoDB not suck for analytics by twblalock on Sunday July 01, 2018 @09:14PM (#17438694)
You only need to copy the stuff that changed since the last time you copied stuff.

If you are really generating 10TB of data more than a few times a day, you can look into putting it in something like Kafka for real-time consumption by the analytics team instead of batch copying.

Re:How to make MongoDB not suck for analytics by ayw on Sunday July 01, 2018 @09:45PM (#17438803)
You just need to read the oplog, so it only needs to track your saves.

In general, you probably should have at least something in your stack which reads all changes from your DB, at the very least for backup reasons.