Chaos Engineering for Traditional Applications

Not all on-prem applications have a future in the cloud, but can those same on-prem applications leverage cloud-like capabilities to help make them more reliable?

In 2011 Netflix introduced the tool called Chaos Monkey to inject random failures into their cloud architecture as a strategy to identify design weaknesses. Fast forward to today, the concept of resiliency engineering has evolved, creating jobs called “Chaos Engineer.” Many companies like Twilio, Facebook, Google, Microsoft, Amazon, Netflix, and LinkedIn, use chaos as a way to understand their distributed systems and architectures.

But all of these companies are based on cloud-native architectures, and so the question is:

Can Chaos Engineering be applied to traditional applications that run in the data-center and will probably never be moved to the cloud?

Continue reading

The Cloud Dilemma

What to do with traditional on-prem applications that don’t appear to have a path to the cloud?

“My app can’t be moved to the cloud…..it is based on AIX or IBMi…….”

What is implied is that the app owner doesn’t want to re-engineer their application to all use cloud-native services, but instead wants to do a classic lift-and-shift of their application without making any application code changes. Since IBMi (AS/400) and AIX are based on PowerPC and not x86, the path the cloud is not apparent for these types of applications.

Continue reading