argo
n8n
Our great sponsors
argo | n8n | |
---|---|---|
43 | 296 | |
14,282 | 40,455 | |
1.5% | 3.5% | |
9.8 | 10.0 | |
1 day ago | 7 days ago | |
Go | TypeScript | |
Apache License 2.0 | Apache 2.0 with Commons Clause |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
argo
-
StackStorm โ IFTTT for Ops
Like Argo Workflows?
https://github.com/argoproj/argo-workflows
-
Creators of Argo CD Release New OSS Project Kargo for Next Gen Gitops
Dagger looks more comparable to Argo Workflows: https://argoproj.github.io/argo-workflows/ That's the first of the Argo projects, which can run multi-step workflows within containers on Kubernetes.
For what it's worth, my colleagues and I have had great luck with Argo Workflows and wrote up a blog post about some of its advantages a few years ago: https://www.interline.io/blog/scaling-openstreetmap-data-wor...
-
Practical Tips for Refactoring Release CI using GitHub Actions
Despite other alternatives like Circle CI, Travis CI, GitLab CI or even self-hosted options using open-source projects like Tekton or Argo Workflow, the reason for choosing GitHub Actions was straightforward: GitHub Actions, in conjunction with the GitHub ecosystem, offers a user-friendly experience and access to a rich software marketplace.
-
(Not) to Write a Pipeline
author seems to be describing the kind of patterns you might make with https://argoproj.github.io/argo-workflows/ . or see for example https://github.com/couler-proj/couler , which is an sdk for describing tasks that may be submitted to different workflow engines on the backend.
it's a little confusing to me that the author seems to object to "pipelines" and then equate them with messaging-queues. for me at least, "pipeline" vs "workflow-engine" vs "scheduler" are all basically synonyms in this context. those things may or may not be implemented with a message-queue for persistence, but the persistence layer itself is usually below the level of abstraction that $current_problem is really concerned with. like the author says, eventually you have to track state/timestamps/logs, but you get that from the beginning if you start with a workflow engine.
i agree with author that message-queues should not be a knee-jerk response to most problems because the LoE for edge-cases/observability/monitoring is huge. (maybe reach for a queue only if you may actually overwhelm whatever the "scheduler" can handle.) but don't build the scheduler from scratch either.. use argowf, kubeflow, or a more opinionated framework like airflow, mlflow, databricks, aws lamda or step-functions. all/any of these should have config or api that's robust enough to express rate-limit/retry stuff. almost any of these choices has better observability out-of-the-box than you can easily get from a queue. but most importantly.. they provide idioms for handling failure that data-science folks and junior devs can work with. the right way to structure code is just much more clear and things like structuring messages/events, subclassing workers, repeating/retrying tasks, is just harder to mess up.
-
what technologies are people using for job scheduling in/with k8s?
Argo Workflows + Argo Events
-
What are some good self-hosted CI/CD tools where pipeline steps run in docker containers?
Drone, or Tekton, Argo Workflows if youโre on k8s
-
job scheduling for scientific computing on k8s?
Check out Argo Workflows.
- Orchestration poll
- What's the best way to inject a yaml file into an Argo workflow step?
-
Which build system do you use?
go-git has a lot of bugs and is not actively maintained. The bug even affects Argo Workflow, which caused our data pipeline to fail unexpectedly (reference: https://github.com/argoproj/argo-workflows/issues/10091)
n8n
- Dify, a visual workflow to build/test LLM applications
-
Helm 101: Creating Helm Charts
A startup, "DevOps Solutions" adopts Helm to streamline their Kubernetes deployments. You're a consultant tasked with creating a basic Helm Chart for n8n. It should be customizable for different environments using values.
- IFTTT is killing its pay-what-you-want Legacy Pro plan
-
A Year of Self-Hosting: 6 Open-Source Projects That Surprised Me in 2023
n8n.io - a powerful workflow automation tool
-
Open Source alternatives to tools you Pay for
N8N - Open Source Alternative to Zapier
- Ask YC: tracking events platform and no-code workflow
-
Your privacy is optional
N8N - anything that I would have used Zapier or IFTTT for I now use N8N. It is a bit harder to use but more powerful.
-
To whoever uses Supabase as their backend: what's your full no-code / low-code stack?
I'm using Weweb as my front end and Supabase as my back end. I'm also looking into n8n.io to run some of the backend logic that I'm either unsure how to code myself within Supabase or unsure if Supabase can perform those back-end tasks and workflows. Curious what stack or tools other Supabase users are using?
-
Show HN: Keep โ GitHub Actions for your monitoring tools
This is similar to something I saw before: https://n8n.io
- FLaNK Stack Weekly 28 August 2023
What are some alternatives?
temporal - Temporal service
Node RED - Low-code programming for event-driven applications
keda - KEDA is a Kubernetes-based Event Driven Autoscaling component. It provides event driven scale for any container running in Kubernetes
Huginn - Create agents that monitor and act on your behalf. Your agents are standing by!
Airflow - Apache Airflow - A platform to programmatically author, schedule, and monitor workflows
flyte - Scalable and flexible workflow orchestration platform that seamlessly unifies data, ML and analytics stacks.
StackStorm - StackStorm (aka "IFTTT for Ops") is event-driven automation for auto-remediation, incident responses, troubleshooting, deployments, and more for DevOps and SREs. Includes rules engine, workflow, 160 integration packs with 6000+ actions (see https://exchange.stackstorm.org) and ChatOps. Installer at https://docs.stackstorm.com/install/index.html
budibase - Budibase is an open-source low code platform that helps you build internal tools in minutes ๐
lens - Lens - The way the world runs Kubernetes
Home Assistant - :house_with_garden: Open source home automation that puts local control and privacy first.