Continuous delivery is a huge step forward in our ability to rapidly deliver features and value to the users of distributed applications, but it comes with a cost and a responsibility. Most modern web applications need to be highly available, and this also means that it should be up during the deployments. Dealing with zero-downtime deployments is a challenge, and there is no easy solution. Moreover, the solutions available vary based on the number of integrated clients, which parts of the World it addresses, how many active users it has... Isn’t there a simple way to figure out how to get there?
Join us to get into the details of the key steps on your path to zero downtime deployments. Learn about the patterns, practices and techniques that make it easier, such as semantic versioning and blue/green deployments. We’ll also walk through an end-to-end demo of how a high traffic web application can survive the challenge of deployments.
What seemed insurmountable at the start of the session will be practical and applicable by the time we’re finished, and you should be able to see how to start moving your production application close to the zero-downtime gold standard.
YOU MAY ALSO LIKE:
- Designing Towards Event Sourcing (SkillsCast recorded in May 2019)
- Certified Scrum Master with Abid Quereshi (Online Course on 26th - 28th October 2020)
- Docker Fundamentals with Matt Saunders (Online Course on 1st - 4th December 2020)
- Debugging Containers on Kubernetes with "kubectl debug" (SkillsCast recorded in July 2020)
- How developers are the new security rockstars
Getting Into the Zero Downtime Deployment World
Tugberk is a self-motivated software developer who craves to create great software products and systems and build effective development teams with a decade of software development and technical leadership experience. He is passionate about knowledge sharing and has been trying to do his best by speaking at conferences, writing blog posts, establishing collaboration on open source projects, and authoring a book. He cares about reliability, observability and scalability of the software products he works on as much as caring about the day-to-day happiness, effectiveness, and productivity of the team he works as part of. He also aims to strive for the balance required to have a stable, maintainable and architecturally-accurate software product, and being on the market fast with an iterative approach.