Soooo I think I'm far enough removed from my old job to comment- I worked at Adobe as a lead on a platform engineering team. Another team came to us pushing fo

Soooo I think I'm far enough removed from my old job to comment- I worked at Adobe as a lead on a platform engineering team. Another team came to us pushing for us to adopt StackStorm for autoremediation of our infrastructure. We looked at it, and didn't see it as a good fit for us. The example we were given was "if httpd goes down, restart it". But: - Systemd's built in restarts worked orders of magnitude faster than StackStorm - At higher levels, the Kubelet, Kubernetes workload controllers, and cloud-native services provided fairly robust autoremediation capabilities Despite this, we were still pressured to use it. I think some other team saw my team's success (we eventually ran the infrastructure for a majority of Adobe's services, and I believe that's still true) and wanted to hitch a ride on the rocket. But we never did. Note the wording on that ADOPTERS.md line - that line only applies to one team at Adobe, a company with tens of thousands of employees and services across hundreds of products. I can tell you while I worked there, StackStorm did not seem to be widely used. The website lists connecting various third party services together. I think that makes sense for quickly snapping together vendor services without having to figure out how to wire up their APIs. For cases where we were fully responsible for all the software involved, it was like trying to drive a car from the back seat with pieces of string.