orchest VS hookdeck-cli

You can check out our OSS https://github.com/orchest/orchest

The code example is part of our ELT/data pipeline tool called Orchest: https://github.com/orchest/orchest/

First want to say congrats to the Patterns team for creating a gorgeous looking tool. Very minimal and approachable. Massive kudos!

Disclaimer: we're building something very similar and I'm curious about a couple of things.

One of the questions our users have asked us often is how to minimize the dependence on "product specific" components/nodes/steps. For example, if you write CI for GitHub Actions you may use a bunch of GitHub Action references.

Looking at the `graph.yml` in some of the examples you shared you use a similar approach (e.g. patterns/openai-completion@v4). That means that whenever you depend on such components your automation/data pipeline becomes more tied to the specific tool (GitHub Actions/Patterns), effectively locking in users.

How are you helping users feel comfortable with that problem (I don't want to invest in something that's not portable)? It's something we've struggled with ourselves as we're expanding the "out of the box" capabilities you get.

Furthermore, would have loved to see this as an open source project. But I guess the second best thing to open source is some open source contributions and `dcp` and `common-model` look quite interesting!

For those who are curious, I'm one of the authors of https://github.com/orchest/orchest

Haven't tried it. In its favor, Argo is vendor neutral and is really easy to set up in a local k8s environment like docker for desktop or minikube. If you already use k8s for configuration, service discovery, secret management, etc, it's dead simple to set up and use (avoiding configuration having to learn a whole new workflow configuration language in addition to k8s). The big downside is that it doesn't have a visual DAG editor (although that might be a positive for engineers having to fix workflows written by non-programmers), but the relatively bare-metal nature of Argo means that it's fairly easy to use it as an underlying engine for a more opinionated or lower-code framework (orchest is a notable one out now).

If you’d like to try something for you data workflows that’s vendor agnostic (k8s based) and open source you can check out our project: https://github.com/orchest/orchest

You can find it here: https://github.com/orchest/orchest Convenience install script: https://github.com/orchest/orchest#installation

We automatically provide container level parallelism in Orchest: https://github.com/orchest/orchest

For people in this thread interested in what this tool is an alternative to: Airflow, Luigi, Kubeflow, Kedro, Flyte, Metaflow, Sagemaker Pipelines, GCP Vertex Workbench, Azure Data Factory, Azure ML, Dagster, DVC, ClearML, Prefect, Pachyderm, and Orchest.

Disclaimer: author of Orchest https://github.com/orchest/orchest

Hookdeck | https://hookdeck.com| Remote- CAN | Backend DevOPs

We are seeking an experienced Backend/DevOps professional who has a passion for working with and optimizing databases, and who has hands-on experience with high concurrency and high throughput systems. We are a small team of 9, operating completely remotely and without a schedule.

We help developers spend less building and troubleshooting issues with their webhooks to focus on their products instead. We offer a complete infrastructure to develop, test, receive, distribute and monitor webhooks and asynchronous events.

If you are looking to be part of an early founding team, fully leverage your knowledge & talent, have an impact and work on hard scaling and concurrency challenges then this might be for you.

We are offering competitive compensation & generous stock options. Here are the roles that are currently open:

- Backend/ Dev OP (must be in Canada)

Hookdeck | Growth Engineering Team | Remote | https://hookdeck.com/

Hookdeck is building out the Growth Engineering team to help us improve the user experience across the entire funnel. We are a small team of 9, operating completely remotely and without a schedule.

We help developers spend less building and troubleshooting issues with their webhooks to focus on their products instead. We offer a complete infrastructure to develop, test, receive, distribute and monitor webhooks and asynchronous events.

If you are looking to be part of an early founding team, fully leverage your knowledge & talent, have an impact and work on hard scaling and concurrency challenges then this might be for you.

We are offering competitive compensation & generous stock options. Here are the roles that are currently open:

- Growth Engineer

Hookdeck (https://hookdeck.com) | Product Eng, Growth Eng, Backend Eng | Full-Time | Remote (World)

Hookdeck is an infrastructure to consume webhooks simply & reliably. Incoming webhooks are challenging because they require a well-built (and often complex) asynchronous system. We help developers spend less building and troubleshooting issues with their webhooks to focus on their products instead. We offer a complete infrastructure to develop, test, receive, distribute and monitor webhooks and asynchronous events.

If you are looking to be part of a early stage team, fully leverage your knowledge & talent, have an impact on the product experience and implement features from scratch then this might be for you!

We are offering competitive compensation, generous stock options and liberty over your geo & schedule.

We are looking forward to hearing from you! Email me at [email protected]

Shameless plug: if you like the development experience of webhooks at Stripe we offer the same experience on our platform at https://hookdeck.com/ which you can drop in to help you add reliability and a better developer experience to receiving webhooks from anywhere.

This is a fantastic resource! Thank you to the folks at ngrok for putting this together! As this site makes clear: webhooks are harder than they appear. Even just consuming webhooks it's easy to get bogged down dealing with issues around rate limits or recovering from bugs that cause missed events! Missed events being particularly painful with platforms that don't offer replay / retry.

Disclaimer: I work at https://hookdeck.com/ & I shamelessly plug our tool for giving you an awesome developer experience working with webhooks and helping deal with some of the concerns brought up on webhooks.fyi.

And if you are interested in webhooks at large a couple more resources worth checking out is the awesome-webhooks[1] list and the r/webhooks[2] subreddit (I just got ownership of the sub and started dusting it off this week after being neglected for the past few years! Please, come join!)

[1] https://github.com/realadeel/awesome-webhooks

[2] https://www.reddit.com/r/webhooks/

and then went throught the codebase: https://github.com/hookdeck/hookdeck-cli

Might I recommend Hookdeck as well?

https://hookdeck.com/

Very very useful for handling webhooks and making working with them including locally a pleasure.