These are chat archives for Automattic/mongoose

17th
May 2016
Joshua Bemenderfer
@JoshTheDerf
May 17 2016 16:23
Additional question: during pre('find' is it possible to modify the result of the query? (So far I've only been able to do it by clearing the results array passed in and filling it with new entries.)
Pier-Luc Gagnon
@Nepoxx
May 17 2016 18:50
We can't use .stream() with aggregate? :/
Pier-Luc Gagnon
@Nepoxx
May 17 2016 19:30
oph wait, doesn't make much sense
LeonineKing1199
@LeonineKing1199
May 17 2016 22:02
So, I started reading about replica sets in Mongo.
Jesus...
It just seems so... Bleh.
This is the wrong approach to distributed computing, guys.
Joshua Bemenderfer
@JoshTheDerf
May 17 2016 22:12
@LeonineKing1199 RethinkDB on the other hand.... :3
LeonineKing1199
@LeonineKing1199
May 17 2016 22:13
I'll have to read up on that. My problem with replica sets is that they serialize all writes through a primary instance of the mongo daemon. That's fine. But the problem is, it seems like the primary can be super-saturated with write requests. This aids in creating replication lag.
And even then, what's the point of "high availability" if like half of all database accesses are writes anyway!
You have serialized writes no matter what but the awfulness that reads may be behind!
What's the point of even horizontally scaling anyway? Not everything should be parallelized!!!!