Why I think Mongo is to Databases what Rails was to Frameworks // RailsTips by John Nunemaker

Strong statement, eh? The more I work with Mongo the more I am coming around to this way of thinking. I tell no lie when I say that I now approach Mongo with the same kind of excitement I first felt using Rails. For some, that may be enough, but for others, you probably require more than a feeling to check out a new technology.

1. Migrations are Dead
2. Single Collection Inheritance Gone Wild
3. Array Keys
4. Hash Keys
5. Embedding Custom Objects
6. Incrementing and Decrementing
7. Files, aka GridFS
(Link: Why I think Mongo is to Databases what Rails was to Frameworks // RailsTips by John Nunemaker)

Advertisement

No comments yet... Be the first to leave a reply!

Leave a Reply

Fill in your details below or click an icon to log in:

Gravatar
WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Connecting to %s

Follow

Get every new post delivered to your Inbox.