dm_mongodb

5 ms·

31.
by dm_mongodb 16y ago
It's ads served per second by DART. Doesn't count adwords, adsense. It is served from several data centers and this is the total.
32.
300,000 requests / second(qos.doubleclick.net)
62 points by dm_mongodb 16y ago|21 comments
33.
by dm_mongodb 16y ago
this blog post talks a bit about a real world implementation and when they do and do not use memcached with mongodb: http://www.businessinsider.com/how-we-use-mongodb-2009-11
34.
by dm_mongodb 17y ago
I have to say I'm not quite clear on difference between a graph db and object db.
35.
by dm_mongodb 17y ago
but I live in Manhattan
36.
by dm_mongodb 17y ago
it can run in a very small footprint. the one gotcha is that as it uses memory-mapped files, you need 64 bit OS for multi-GB databases.
37.
by dm_mongodb 17y ago
you may be right that i've overgeneralized to the other products based on my experience with mongodb; all i know for sure is mongodb has some nice properties here.
38.
by dm_mongodb 17y ago
Preferred and typical use of MongoDB is with no javascript in the queries. There really is a huge reduction of risk for this one particular attack.
39.
by dm_mongodb 17y ago
trying to understand what you just said: do you mean they may have buffer-overrun vulnerabilities, just as they are new projects? a lot of nosql projects are written in erlang and java btw.
40.
by dm_mongodb 17y ago
a nice side-benefit of nosql databases is this massively underestimated problem (usually, depends on the product) going away
41.
by dm_mongodb 17y ago
Sharding is use with replication to provide failover. This will be more automated in the upcoming sharding beta. Key storage in the document objects make it more 'schemaless' which is actually incredibly useful; the document format (BSON)
42.
by dm_mongodb 17y ago
concurrency is much better in the newest versions
43.
by dm_mongodb 17y ago
this touches on some related aspects: http://blog.mongodb.org/post/307919034/partial-object-update...