Chaos Engineering

Chapter 8. Capital One Adoption and Evolution of Chaos Engineering

Raji Chockaiyan

Chaos Engineering provides a point of view of embracing failure and learning about the system’s weakness from those failures. In the cloud native environment, this way of developing software cannot be ignored. Cloud native systems accept that failure can happen at any time and we will need to engineer and build robust systems that can withstand a full range of failures. Compared to industries that have less regulation, software in the financial services sector comes with a few more layers of complexity to take into consideration. During a system failure, a single parent could be applying for a loan for their first house, another customer might be trying to transfer funds using their mobile device, and a student could be applying for their first credit card to start building credit history. Depending on the size of the failure, the impact would range from a mild annoyance to bitter detachment to the brand, negatively reflecting on the reputation of the financial institution and potentially affecting the business.

Additionally, there are governing bodies related to how banks do their business. Necessary audit trails need to be maintained and submitted periodically to financial regulators, including the Office of the Comptroller of the Currency (OCC), the Consumer Financial Protection Bureau (CFPB), FinCEN, the Federal Trade Commission, and the Department of Justice. The effect is any change in the ...