Armory Blog

Traditionally, deploying changes to a company’s applications has been a difficult and scary affair, which has motivated companies to build monolithic apps that are updated as infrequently as possible, with each update being a complicated firedrill coordinated across many teams (and often done on Friday night, so teams can spend the weekend cleaning up the […]

Today, Netflix and Google announced Kayenta, the open-source project that codifies 5+ years of learnings from Netflix & Google on how to effectively canary deployments in global, high traffic environments. Kayenta works seamlessly with Spinnaker, which powers the Core of Armory’s platform. Armory has been involved in Kayenta for the past few months. We contributed […]

Isaac Mosquera, Armory’s CTO, recently gave a talk at Atlassian’s Mountain View office for LaunchDarkly’s Test In Production Meetup. Isaac talks about how using automated canary analysis is a way to limit the blast radius of issues in production while increasing development productivity, reducing risk and keeping developers happy. You can learn more about canary […]

Feature flags and canaries have different objectives despite appearing similar: Feature flags expose a specific feature to a sample set of users and then measures it’s impact. Canaries expose a specific version of the entire application to a sample set of users and then measures it’s impact. So what’s the difference? Here’s the high-level: Feature […]

Canary Deployments: For monitoring test deployments on a small percentage of servers before scaling the changes to the rest. When would I use it? When testing a new batch of code or deployments that may or may not break your servers, it should be good practice for developers to push the code to a small […]