inngest VS OpenFaaS

The executor, queue, state, drivers, etc. are all on Github (https://github.com/inngest/inngest).

Over the last year we've been iterating on the internals a lot to build things like:

- Concurrency (shared nothing, auto-scalable)

- Batching (have one fn run with 100 events, vs 1:1 mapping)

- Prioritization

- Replay

- Parallelization

The churn has been really high, and it would be really hard for people to handle this migrations being self hosted. Now that this is slowing, it's realistically something that's possible soon.

Feel free to comment here or on Github at https://github.com/inngest/inngest.

Ha, knew this would come up. We have an issue to move code to GPL after some time: https://github.com/inngest/inngest-cli/issues/136.

You can use something like https://github.com/inngest/inngest-cli to run golang-based functions as a queue without infra.

Serverless functions are now offered by many cloud providers, as well as having options like OpenFaaS, Knative, Apache's Openwhisk and more from the open source community that run in environments ranging from one server all the way up to globally replicated private clusters.

OpenFaaS

Did you consider running knative or openfaas? https://github.com/openfaas/faas

Anyone knows other alternatives for Azure Functions, but for DIY hosting? ( eg. OpenFaas - https://www.openfaas.com/ )

Maybe OpenFaaS with grafana and slack notifications for non-200 responses?

OpenFaaS - https://www.openfaas.com

By the way, if your organization is leveraging EKS as a platform and your DevOps team is willing to enable this operator, there's an exciting tool called OpenFaaS. Essentially, it enables you to host your Lambda functions on your own infrastructure instead of relying on the public cloud provider.

This is where I see K8S coming in – teachers can provide dev deployments that are setup for students to learn. Teachers can also provide containers that run automated tests against the student containers for assessment! Plus, we can smooth over some of the git workflow stuff for the ripest of beginners; we can integrate with github to sync their work on our platform to repositories on their github account, so that they can really take ownership of the work they do on the platform. Last, students can graduate their work from development into production very easily, since we can take the base images + student diffs, build a new "prod" image for the student. We can run students' prod work on "serverless" K8S frameworks like fission or OpenFaas to be able to host many low-traffic "production" apps at the same time.