News for hackers. Stuff that matters.
Re:StackStorm – IFTTT for Ops by buro9 on Sunday November 05, 2023 @09:09AM (#38151247)
this looks ace, so a serious question: is it widely used?

this is the first I've seen of it (seems true of other people commenting too), but it looks like there's some strong history (several acquisitions, then joined Linux Foundation in 2019)... so why hasn't it achieved greater visibility?

those questions are not asked to rain on someone's parade, but because going all-in on automation and workflow is a gamble as to whether that thing that glue is going to stick around (Linux Foundation suggests yes), and also is a skill that people want to learn and use (being widely adopted and something people can apply to other companies and roles would make this so, hence the questions)

Re:StackStorm – IFTTT for Ops by wahnfrieden on Sunday November 05, 2023 @09:56AM (#38151647)
it's been around a long time with serious usage, hn frontpage just doesn't typically provide a thorough market analysis perspective and indeed has many non-expert (in terms of gained familiarity with a correctly broad view of our field) members. still doesn't mean it's necessarily a great choice though
Re:StackStorm – IFTTT for Ops by Reventlov on Sunday November 05, 2023 @09:57AM (#38151653)
> this looks ace, so a serious question: is it widely used?

I know some french cloud provider that uses it, and… I'm not sure they're happy with it. Issues with YAQL, a lot of weird bugs. They mentioned Temporal looking much cleaner.

Re:StackStorm – IFTTT for Ops by pmetrix on Sunday November 05, 2023 @11:46AM (#38152790)
They have a list of ADOPTERS.md here:

https://github.com/StackStorm/st2/blob/master/ADOPTERS.md

which mentions Adobe, DigitalOcean, Fastly, HP, Verizon and a few more among others already mentioned on the website.

Re:StackStorm – IFTTT for Ops by dharmab on Sunday November 05, 2023 @07:03PM (#38157137)
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.

Re:StackStorm – IFTTT for Ops by j45 on Sunday November 05, 2023 @11:51AM (#38152850)
If you scroll down it’s listed right there: Cisco, NASA, Netflix, Pearson

It feels a little different than n8n but I can’t tell the differences at first glance.