When we began hacking away on Hudl we chose SQL Server as our database. After a few years and solid company growth we realized SQL Server was quickly becoming a bottleneck. Because we run in EC2, vertically scaling our DB was not a great option. That’s when we began to look at NoSQL seriously and specifically MongoDB. We wanted something that was fast, flexible and developer-friendly. In this post we’ll take a look at our schema design choices, our migration plan and the performance we’ve seen with MongoDB.
We’re working on a brand-new basketball product here at Hudl. It’s an extremely exciting opportunity for our company—we’re creating a whole new way of capturing, consuming, and analyzing basketball video. The 2013-14 basketball season was my first beta at this scale, and I’d be lying if I told you we had a flawless strategy and executed perfectly from every angle. The team and I learned some valuable lessons during the course of this season that I’d like to share with you in this post.