MongoDB and CAP

Just read this great post, Call me maybe: MongoDB and the wrap-up post, Call me maybe: final thoughts. They're part of a series called Jepsen on behavior of various NoSQL databases in failure scenarios.

Very geeky but very interesting.

Completed MongoDB M102

As I mentioned earlier, I signed up for "M102: MongoDB for DBAs". Great class.

I just completed it yesterday and got 100% on everything, homework and final.

If you're interested in learning about MongoDB, this is a great way to get a broad exposure in a limited amount of time. Because it includes weekly lectures and homework, you can't procrastinate like you can with that technical book on your desk that you planned to read through.

Speaking at Data Modeling Zone 2014

My boss, Ryan Smith, and I will co-present on modeling in NoSQL at Data Modeling Zone 2014 here in Portland.

It's not until October of next year, so we don't have things nailed down yet, but it will be fun to work with Ryan on this.

RESTful Service Best Practices

I was recently looking for reference material to back up my preference for storing date/time values in MongoDB in UTC using MongoDB's ISODate type. I found this great reference published at amazonaws.com:

RESTful Service Best Practices
Recommendations for Creating Web Services

It gives a solid recommendation for RESTful services:

"... always use the same format, including the time portion (along with timezone information) in the string. ISO 8601 time point format is a good solution, using the fully-enhanced format that includes hours, minutes, seconds and a decimal fraction of seconds (e.g. yyyy-MM-dd'T'HH:mm:ss.SSS'Z')."

It doesn't directly address storage directly, but it's such a great resource, I wanted to share it.