Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

MongoDB: 5 Syntactic Weirdnesses to Keep in Mind

DZone's Guide to

MongoDB: 5 Syntactic Weirdnesses to Keep in Mind

· Big Data Zone
Free Resource

Effortlessly power IoT, predictive analytics, and machine learning applications with an elastic, resilient data infrastructure. Learn how with Mesosphere DC/OS.

People like to complain about MongoDB. For instance, maybe they feel that it ruined their social network, or any number of other less recent complaints. The debate gets so heated, though, that sometimes valid criticisms - and nothing is above criticism - are dismissed as bandwagon hatred. It's a problem that Slava Kim seems very aware of in this recent blog post on some of the syntactic weirdnesses of MongoDB. It's not bashing, Kim stresses. For developers to effectively use any technology, they need to understand the "sharp edges."

Kim goes into detail for each warning, covering five general areas:

  1. "Keys order in a hash object"
  2. "undefined, null and undefined"
  3. "Soft limits, hard limits and no limits"
  4. "Special treatment for arrays"
  5. "$near geo-location operator"

Check out the full article for all the details on what aspects of MongoDB may cause some problems or frustration down the line.

Learn to design and build better data-rich applications with this free eBook from O’Reilly. Brought to you by Mesosphere DC/OS.

Topics:

Opinions expressed by DZone contributors are their own.

THE DZONE NEWSLETTER

Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

X

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}