Back in 2012, Quid made the decision to invest resources into automating our infrastructure with Chef. A few years later, we have around 40 machine types spread over 400 machines powering our development and production environments. Thanks to our now well developed cookbooks, we can rest easy should any machine need to be recreated. With over 3 years of experience under our belt, we’d like to share some of the ups and downs of cooking with Chef. The ups The community artifacts When Chef first started gaining real popularity, the technology was really rough around the edges. A community latched on anyways and has produced methodologies and artifacts which not only shifted Chef development but likely most future configuration management tools going forward. The Chef community produces and maintains an impressive number of cookbooks covering anything remotely popular. Resources like Bryan Berry’s Food Fight Show, Jaime Winsor’s environment pattern, and Chef’s conference talks heavily shaped Quid’s Chef practices. We are forever grateful. Flexible and powerful fundamentals Even if you do not appreciate all the cooking analogies, Chef has done a very good job at providing flexible yet powerful capabilities with their server, environment, node, and cookbook setup. We can easily […]Read More
- How does Quid create reliable business intelligence?
- Our First Engineering Game Day
- Improving search with Word2Vec and Wikipedia
- Managing text data you haven’t seen and can’t control
- Using deep learning with small data
- It’s NOT the Stork: Where Tests Come From
- Quid Hackathon II
- Here’s a suggestion
- Optimizing The Rendering Engine
- Quid Hackathon
- Major League Data Visualization Event @ Quid!
- The Ups and Downs of a Chef Shop
- Reaching Equilibrium in Web Browser Network Visualizations