[dylburger]

Yes we're thinking a lot about this. The vision would be let you execute workflows on whatever function runtime you use. So you'd have one definition of a workflow on Pipedream, but that could be serialized to e.g. a Google Cloud Function, an OpenFAAS function, etc. And you'd get to run it in your own VPC, with access to your own internal resources, without relying on Pipedream's infra.

Still in the idea phase, but let me know if that resonates.

[alexellisuk]

Hey, I'm the maintainer of OpenFaaS. Thanks for mentioning the project.

Pipedream v1 ran on Lambda, but this post is touted as "AWS Lambda alternative", have you moved off the AWS Lambda platform?

I was curious how you added support for other languages, was it in the same way that you built-in support for Node.js? Where all the code gets effectively built into a single Lambda function and proxied?

For people who want to call OpenFaaS workloads from Pipedream, that's possible over HTTP and Pipedream makes that relatively simple. One thing I think they've really nailed is the OAuth integration, it just makes that whole painful flow a lot more convenient. I also like the editor and the way it infers what kind of input will go into the next step in a workflow.

Alex

[dylburger]

Hey Alex!

We build our own containers and still run them on Lambda. The container base image contains the necessary language runtimes so that we can execute both Node.js and e.g. Python in the same workflow.

Do you think it would make sense to add an OpenFAAS integration to Pipedream? Then it would show up when users searched for it in workflows, and have a dedicated page at https://pipedream.com/apps . Even if we just end up wrapping HTTP requests to kick off a function, we've found it's helpful because users are often searching for FaaS platforms by name when they want to integrate with them in a workflow.

[toomuchtodo]

It does resonate, thank you!