Running sites with high availability is a foregone conclusion for most businesses. There are plenty of blog posts and articles out there talking about “nines”, but few really describe how to actually measure availability. Five nines of what, exactly? How do you measure continuous uptime of a website that serves discrete HTTP requests? Here’s how we measure server-side availability both overall for our individual microservices on hudl.com.
One part of Hudl I frequently have to explain to people outside the company is the structure of our product team. Fellow developers at other companies, friends I graduated with, and plenty of people in between want to know how Hudl works—and as it turns out, there’s a lot to talk about. We’re constantly evolving and learning more about how to keep our heads on straight, and as we do, we want to get the lessons learned on the table.
Automated testing is a critical part of our deploy process at Hudl. We rely on it for feedback during deploys to production as well as our test environments. We started down the path of using automated regression testing about 2 years ago, early on trying various products until we found the right fit. We feel we have learned a lot during this time and made our process better and want to share our experiences.
Quality Assurance is a crucial part of the software development process. But as a novice, it can seem daunting and unclear. After all, QA is responsible for ensuring the product is ready for the masses. What if I miss something? Where do I even begin with my testing? These were questions that plagued me at first. It took a month, but eventually I found myself growing more confident in my testing abilities and the impact I could make on Hudl’s products.