4 ms·
We're using MongoHQ and have been for around a year. 1) We're outside of the AWS infrastructure, the latency is bearable esp. with caching. If you can cache i
by benologist 15y ago
We're using MongoHQ and have been for around a year.
1) We're outside of the AWS infrastructure, the latency is bearable esp. with caching. If you can cache it then the latency straight away only matters a small % of the time.
2) Local mirroring is coming I believe, at which point you can have a constant failsafe although their uptime & reliability has been great in our time with them.
- startupcto 15y agoWhy are you even using MongoHQ and have to live with bearable latency? I mean if you don't even use AWS, why not just deploy your own db server?
- benologist 15y agoGood question. Originally I did do it all myself, I installed it and I had replication and all that set up, but it fell over and until you have a bunch of experience that means you're a noob who has to dick around in Google and IRC looking for answers for every simple problem, while part or all of your platform is broken. Our servers are already in multiple datacenters which means we can either maintain our own multi-dc MongoDB cluster (not really an option w/ me at the wheel) or we have to eat some latency anyway. In my opinion it's cheaper + easier to let MongoHQ handle it all, and latency .. as long as it's measured in milliseconds it's acceptable compared to doing it all myself.