Marcus -- the short answer is included in the
readme.md for
Simian Army:
- Chaos Monkey is now standalone
- Janitor Monkey is replaced with Swabbie
- Conformity Monkey and auditing services like it have moved directly into Spinnaker
Slightly longer answer: all software has a lifecycle and it was time to evolve the core ideas of Simian Army to match the changing needs of Netflix's environment. The most obvious first step was to separate out the services so that they could evolve independently. By separating them it also enabled each to use different technologies and deployment models, for example embedding Conformity Monkey functionality directly into Spinnaker provides teams feedback in the same UI they do deployments, increasing the visibility of violations while enabling the ability to surface corrective actions.
We have an older
blog post of how we build code at Netflix. Although it is from 2016 it still fundamentally represents the way we deploy code for many services. The biggest change since 2016 is the impact of
containers in our code-build-deploy pipeline.
Hope this helps with your research.
Thanks,
Ed.