By: Stephen Welsh
3 min read
Chase is planning for a significant workload migration of its systems to Amazon Web Services (AWS) over the coming years.
We have the opportunity to not only take advantage of the modern infrastructure with cloud, but also to design well-architected systems once we modernize our applications. But to achieve success with an AWS system and take full advantage of the processes to deliver software to AWS, we will have to align core concepts and definitions with the industry best practices. In this three-part series, I’ll focus on the availability concept of resiliency and the testing of availability through chaos experiments, then discuss how to establish availability requirements and add them to the deployment module in SEAL.
Resiliency Process within PtX and Deploying Resiliency and Chaos Testing
We established the Permit to X (PtX) process to verify and validate a minimum set of requirements (largely nonfunctional requirements) are met before a new application component, module or service is allowed to take customer traffic. The milestones are Permit to Build (PtB), Permit to Deploy (PtD) and Permit to Operate (PtO). In this post, we will go deeper into the AWS Well-Architected Reliability Pillar and how it will align with the PtX process in greater detail.