How We Stay Sane with a Large AWS Infrastructure
We’ve been running hudl.com in AWS since 2009 and have grown to running hundreds, at times even thousands of servers. As our business grew, we developed a few standards that help us make sense of our large AWS infrastructure.
Mar 16, 2016
Faster and Cheaper: How Hudl Saved 50% and Doubled Performance
We took time to optimize our EC2 instance types. By finding the maximum load a server could handle we were able to run a quarter as many app servers. Our hourly spend dropped by 50%. Despite the huge cost savings, we also saw a 2x improvement in response times! This came about by moving to a newer instance family.
Aug 14, 2015
Betting the Farm on MongoDB
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.
Apr 30, 2014
C# + RabbitMQ = Happy Servers
At Hudl we use RabbitMQ to help us decouple some operations from impacting normal web requests. We smooth out spikes in write traffic and isolate long-running or CPU-intensive tasks. RabbitMQ is fast, full-featured, and offers good management/monitoring features.
Nov 11, 2013
Logging All the Things
Logging in your application is super important. Early on it’ll be fine to peruse your logs manually. As traffic increases you’ll soon have a need to aggregate all that data into one place so it can be easily searched. At Hudl, we chose Splunk. There are a lot of competing products, but it works well for us. Either way my advice is clear: Log. All the things. You won’t regret it.
Aug 26, 2013