How to Survive Deployments and Not Disrupt Your Users
Our panel of experts shared their experiences on delivering high performing, scalable, and reliable software to the web.
We answered your questions on code reviews, profiling, versioning, automation testing, rollout strategy, disaster recovery, and zero-downtime deployments.
Kaelen Proctor — Software Architect
Kaelen has been a part of the evolution of the Achievers platform over the past 5 years. He’s tackled challenges in resolving performance through profiling tools, scaling the system across multiple shards and data centers, and most recently how to write maintainable and testable code.
Ross Murphy — Engineering Team Lead
Ross joined Achievers over 3 years ago spending the better part of 2 years working as a part of the release team where he implemented and improved deployment processes, led the charge on code deploys and reverted bad commits. He now works as an engineering team lead and gets to build awesome new features.
Carrie Tanguay — Release Manager
Carrie Tanguay has been the Release Manager with Achievers for the last 3 years and has been with the company for over 5 years. As the first Release Manager at Achievers, Carrie has developed and implemented several key release and change management processes, based on ITIL best practices. This release framework has allowed Achievers to continually scale, improve and execute our releases with a focus on “zero-downtime deployments” and seamless updates for our end-users.
Stephen Griffin — Principal IT Engineer
Stephen has been working in the SaaS space for over 12 years. For the last decade he’s been building and scaling out infrastructure for cloud environments. Most recently at Achievers, he’s lead a team to add a new data center from conception to implementation in only 4 months.
Michelle Chen — Senior Software Developer & Panel Moderator
How to Survive Deployments and Not Disrupt Your Users was originally published in Achievers Tech on Medium, where people are continuing the conversation by highlighting and responding to this story.