Chaos Engineering is fault injection being incorporated as a core aspect of a production system. So whereas in the 1970s fault injection might have been more used in the development and test phases, Chaos Engineering also includes a bunch of persistent services knocking out key aspects of your production system.
So basically you are writing tests that break things, and then keeping that code in the final compile?
Wherein the table is made, then shattered, but keeps its functionality :)
Mostly better marketing... I'll bet "Chaos Engineers" get paid two or three times whatever the role that did "fault injection" got.
Fault injection is a technique. Chaos engineering is a discipline.
Yes; to expand on that a bit -- you can do fault injection in a chaos experiment. You can also do many other things within an experiment that would be difficult to classify as fault injection; for example, a sharp increase in the number of customers making requests to your service isn't really a fault. Chaos Engineering then wraps all of those techniques in a framework of experimentation and analysis. That's the discipline, which encourages you to proactively make improvements to Availability, and now Security as well.