Suggest modification to this talk

Title

Description

By, Adrian Pike
Remember when Heroku showed up and how much it changed our world? Suddenly a simple `git push` and my app was online. Gosh, those were the good days, weren't they? Things have gotten a little more complicated for us these days. We've got inter-service dependencies. We should be doing some rolling deploys and user segmentation. Rollbacks should be instant and trivial. What about staging environments, why not be able to roll code safely? As an engineer, I should just be able to `git push`, and get back a running app instance. I should be able to route traffic to it whenever and however I want, whether it's production, staging, internal test, or just a running code spike on production servers to show a colleague. In this talk, I'm going to talk about the tools and infrastructure that I've built in the past to solve deployment woes for big, thorny, complicated apps, and give engineering teams tons of power. I'll also show off an open-source implementation that I'll be building specifically for RoA.

Help us caption & translate this video!

http://amara.org/v/GUQS/

Date

Summarized using AI?

If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.

Show "Summarized using AI" badge on summary page

Summary

Markdown supported

In his talk titled "Deployment Nirvana," Adrian Pike discusses the evolution of deployment practices, focusing on experiences from his time at Moz and the challenges of service-oriented architecture (SOA). He reminisces about the simplicity of earlier deployment methods, likening it to the ease of deploying applications with just a `git push` akin to Heroku's early days. However, as applications have become more complex, with numerous inter-service dependencies, the deployment process has also become more intricate and challenging.

Key points of the talk include:  
- **Shift to SOA**: The transition from monolithic applications to microservices is driven by the need to manage cognitive load effectively among development teams. Smaller, independent services allow developers to work with well-defined API contracts.  
- **Complexities of Deployment**: While breaking applications into services reduces cognitive overload, it introduces deployment complexities, including managing interdependencies, ensuring reliability, and maintaining smooth operations.  
- **Development Challenges**: Adrian highlights the difficulty in coordinating multiple service updates and versioning, underlining the importance of ensuring all related services remain synchronized during deployments.  
- **Built Tools**: He discusses tools developed at Moz, such as Circus, DMV, Seaport, and Viaduct. These tools helped enable zero-downtime deployments, manage service registries, and streamline the deployment process despite the complexities introduced by microservices.  
- **Open-source Project**: Adrian shares his excitement about an open-source tool designed to facilitate smoother deployments that could be integrated with platforms like Heroku, emphasizing the need for deployment practices to evolve alongside the technologies and architectures used today.

In conclusion, Pike reiterates that while deployment tools and frameworks have improved significantly, ongoing efforts are necessary to simplify deployment processes, reduce complexity, and ensure operational reliability. A long-term strategy is vital to shield engineering teams from the complexities of deployment infrastructure, ultimately enhancing productivity and streamlining workflows.

Adrian's insights reflect a pivotal shift in engineering practices and underscore the continuous journey towards deployment Nirvana, advocating for methods that empower developers while mitigating the overhead of technical intricacies.

Cancel