News for hackers. Stuff that matters.

A comment on MongoDB queries don’t always return all matching documents. Parent comment

Re:MongoDB queries don’t always return all matching documents by PeCaN on Tuesday June 07, 2016 @06:27PM (#11858500)
MongoDB: Because /dev/null doesn't support sharding.
[ Parent | on HN ]
Re:MongoDB queries don’t always return all matching documents by nameless912 on Tuesday June 07, 2016 @06:53PM (#11858657)
But it does support sharting. Your entire app. Into the ether.
[ Parent | on HN ]
Re:MongoDB queries don’t always return all matching documents by brianwawok on Tuesday June 07, 2016 @07:23PM (#11858853)
At webscale
[ Parent | on HN ]
Re:MongoDB queries don’t always return all matching documents by leothekim on Tuesday June 07, 2016 @07:49PM (#11858983)
Ha ha, you said "sharting."
[ Parent | on HN ]
Re:MongoDB queries don’t always return all matching documents by bigiain on Tuesday June 07, 2016 @10:50PM (#11859658)
nc -vv -l 27017 > /dev/null

That and some round robin dns entries should be good enough for prod use, yeah?

('course it's not webscale ready till it's deploayble as a docker container which contains critical nodejs code with a dependancy on leftpad.js...)

[ Parent | on HN ]
Re:MongoDB queries don’t always return all matching documents by PeCaN on Tuesday June 07, 2016 @10:59PM (#11859686)
These days all the cool kids use LPaaS on http://left-pad.io/, it scales much better than running leftpad on a local machine.
[ Parent | on HN ]
Re:MongoDB queries don’t always return all matching documents by jeltz on Wednesday June 08, 2016 @08:26AM (#11861722)
If you use ncat you can even get TLS support.
[ Parent | on HN ]