4 ms·
The #1 enginering design pattern is to obey speed of light transfer of information latency. Moving data into and out of MongoDB has that unavoidable cost, and i
by crb002 9y ago
The #1 enginering design pattern is to obey speed of light transfer of information latency. Moving data into and out of MongoDB has that unavoidable cost, and it is a waste if the only thing you want is JSON formatting of the same data already in your RDBMS.
- Shikadi 9y ago>Speed of light transfer of information latency That's not a thing, at least not in this context or that phrasing.
- Retra 9y agoThat's not a design pattern, it's just a constraint that designs have to account for.
- b4lancesh33t 9y agoOverall latency is important. Where it comes from isn't very important. Transferring data a few light-nanos of distance into or out of a colocated Mongo DB instance simply isn't going to move the needle on any important metric. (Disk IO latency might, but that has little to do with the speed of light.)