fission VS inngest

Fission

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.

I use https://fission.io/ on Kubernetes to emulate AWS Lambda + API Gateway to run Python functions. I use their YAML Spec functionality to deploy functions. It works well for my use case.

After doing a lot of research, I ended up settling on the Fission.io framework to support this project. Fission is an open-source Serverless framework running in kubernetes. Think AWS Lambdas, but we are in control of every part of the infrastructure. Kubernetes gives us the power to define the environments the containers will be executed in, and any other resources they need. This gives us the control we need to be able to create our very own environment for executing arbitrary JavaScript through the V8 engine. Each function can be isolated as much as we need to and Fission is really great at giving us the ability to quickly create multiple environments.

Nope. I was using https://fission.io/

There are a lot of FaaS service offerings out there namely Lambda, Azure Functions, Google Cloud Functions to name a few. While these offerings run on their respective clouds, there are services like Fission that are open source and allow you to deploy and execute functions on Kubernetes clusters irrespective of where they reside.

Fission

It's super slow (20-50 rps), please try this instead : https://github.com/fission/fission (few hundreds to few thousands rps)

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.