DrupalCon Chicago 2011 talk by douggreen and chx on MongoDB and Drupal, see also http://chicago2011.drupal.org/sessions/practical-mongodb-and-drupal

2. #drupalchi, #drupalchimongo for questions

3. http://www.slideshare.net/douggreen/drupalcon-chicago-practical-mongodb-and-drupal

8. Never call a web page from your web page

9. CSS and JS aggregation

10. CDN's

19. Takes best advantage of 2010 Operating Systems that manage memory well

20. Takes best advantage of 2010 Hardware the recognizes disk and memory is cheap

22. Lack of GUI based tools

23. Small user community and new language that must be learned

24. 10gen support is excellent, free and paid (but as with all companies they are seeking ways of funding their efforts, so this is changing)

37. Blocks – conditions in DB instead of code

38. Queues – mostly to avoid another daemon and it's fast enough

39. Watchdog – capped collections, never run out of space, counts and groups by id

40. Cache – not used on Examiner.com

52. We miss relational nature of MySQL with a GUI query reporting tool, all reports have to be programmed.

53. Site uptime is much higher than before, but still have some instability related to an immature product

54. Drupal 7, Field API, DBTNG, MongoDB, and Community are awesome

56. I think MongoDB is a perfect fit for search, and I'm the right guy to do it, but every time I mention this, people say, but we have SOLR, why would you do this?