Mackenzie is the Global Startup Evangelist at AWS. His days are spent traveling the globe to meet startups, share their stories, and connect engineering teams together. Every day there are a large number of startups launching on AWS across every imaginable industry. It’s Mackenzie’s mission to find stories of startups that are helping to improve the world and share these stories with a wide audience.
Join this online series and learn how to build resilient applications using a combination of software and architectural patterns, operational models, and software deployment processes to build, deploy and operate successful applications.
Hear from AWS’s leading experts and AWS Partners on how to reliably maintain and operate your infrastructure and services by revealing operational gaps and preventing regressions.
-Whether you are beginning to build on AWS, or expanding your cloud practice, you will learn how to build, deploy, and operate successful applications
- Builders, IT managers, IT pros and cloud enthusiasts who want to learn the latest trends in resiliency and chaos engineering and would like to equip themselves with insights to drive change and operational success
-Builders who love to experiment on a software system or service to build confidence in its capability to withstand turbulent and unexpected conditions
As applications move online, and automation extends to control more of the world around us, software failures have an increasing impact on business outcomes and safety. We need to develop more resilient systems, and that can’t be left as an operational concern. Resilience needs to be architected into the application code and operability is one of the most important attributes of a resilient system. We’ve seen many examples of failures escalating as a small initial problem causes poorly designed and tested error handling code and procedures to fail in ways that magnify the problem and take out the whole system. What can we do about this? To start with, it’s a shared responsibility to build and operate systems that are observable, controllable, and resilient. With the integration of roles from DevOps practices, and the automation provided by cloud providers, we need to adapt common concepts and terminology that already exist in resilient systems design, for cloud native architectures.
Presenter: Adrian Cockcroft, VP Cloud Architecture Strategy, Amazon Web Services
Once systems are designed, implemented, and tested, we come to what is arguably one of the hardest aspects in the lifecycle of a system: bringing it to life and sustaining it in operations. Learn how to achieve operational excellence by focusing on three crucial interconnecting elements critical to successfully operate the technology we build — culture, tools, and mechanisms.
Presenter: Matt Fitzgerald, Senior Manager, Developer Advocacy, Amazon Web Services
Immutable infrastructure is a model in which no updates, security patches, or configuration changes happen “in-place” on production systems. Immutable infrastructures are more consistent, reliable, and predictable; and they simplify many aspects of software development and operations by preventing common issues related to mutability. In this session, learn why immutable infrastructure is an important concept in software engineering, and see a demo of immutability in serverless architecture.
Presenter: Adrian Hornsby, Principal Developer Advocate, Amazon Web Services
We have traditionally built robust software systems by trying to avoid mistakes and by dodging failures when they occur in production or by testing parts of the system in isolation from one another. Modern methods and techniques take a very different approach based on resiliency, which promotes embracing failure instead of trying to avoid it. Resilient architectures enhance observability, leverage well-known patterns such as graceful degradation, timeouts, and circuit breakers. In this session, we review the most useful patterns for building resilient software systems and especially show the audience how they can benefit from the patterns.
Presenter: Adrian Hornsby, Principal Developer Advocate, Amazon Web Services
Planning and performing chaos experiments on instance- and container-based workloads have been battle-tested by companies of all sizes and industries. However, serverless functions and managed services present different failure modes and levels of abstraction. In this session, we focus on applying chaos engineering principles to serverless, both for serverless functions and managed services. This covers how hypotheses are formed to fit serverless, what the experiments can achieve, and how to perform them practically.
Presenter: Gunnar Grosch, Senior Developer Advocate, Amazon Web Services
In this session you will hear from Canva on how they enable users to collaborate with each other by introducing services that support bidirectional streaming with RSocket. This talk discusses the challenges that Canva faced building these services, and the solutions used to ensure reliability requirements were met.
Presenter: Sergey Tselovalnikov, Software Engineer, Canva
During this session, you will learn how to lower any potential risk "bad" code can introduce to your end product by making sure all of code is tested before making any changes to production. In this session, we will also take a look at some tools, patterns and best practices on how to setup testing pipelines for application delivery. These include patterns such as canary and blue/green deployments and testing for outcomes during production.
Presenter: Darko Meszaros, Amazon Web Services
In this talk, we will look at the tools that AWS provides to add observability into your applications. We will focus on the three pillars of observability – Logs, Metrics and Traces and show the different tools available with code examples and best practices for you to use in your applications.
Presenter: Marcia Villalba, Senior Developer Advocate, Amazon Web Services
With the wide adoption of micro-services and large-scale distributed systems, architectures have grown increasingly complex and can be hard to understand. Worse, the software systems running them have become extremely difficult to debug and test, increasing the risk of outages. With these new challenges, new tools are required and since failures have become more and more chaotic in nature, we must turn to chaos engineering in order to reveal failures before they become outages. In this talk, we will quickly introduce chaos engineering and show the audience how to start practicing chaos engineering on the AWS cloud. We then walk through some of the tools that can used to inject failures in their architecture in order to make them more resilient to failure.
Presenter: Adrian Hornsby, Principal Developer Advocate, Amazon Web Services
How can you practice chaos engineering in a DevOps culture? In this session, we will share examples of integrating chaos engineering into the CI/CD pipeline to facilitate "shifting left". We will also share how chaos engineering can be used to validate monitoring and alerting and improve the observability of services. This session will shares demos practicing CE with containers (Amazon EKS, Docker), Amazon EC2 instances and Amazon CloudWatch. We will conclude this session by sharing chaos engineering success stories customers including Gremlin, NAB, and Mailchimp.
Presenter: Tammy Bryant, Principal Site Reliability Enginee, Gremlin