Fission vs OpenFunction
Fission
fission.ioOpenFunction
openfunction.devSide by side
| Figure | Fission | OpenFunction |
|---|---|---|
| Price from | — | — |
| Free plan | — | — |
| Free trial | — | — |
| Open source | — | — |
| Windows | Yes | — |
| macOS | Yes | — |
| Linux | Yes | — |
| API | Yes | — |
| Self-hosted | Yes | Yes |
| Plans published | 0 | 0 |
| Spec score · Serverless Platforms | 7.7 (#12) | 6.8 (#19) |
| Deployment | Fission deploys functions with one command without requiring users to build containers or manage Docker registries. | Installation requires a Kubernetes cluster and documents deployment using Helm charts. |
| Event sources | The docs list message queue trigger integrations for Apache Kafka, AWS SQS, AWS Kinesis, GCP Pub/Sub, NATS, RabbitMQ, and Redis Lists. | OpenFunction Events lists Kafka, Cron, and Redis as supported event source types. |
| Integrations | The homepage says Fission integrates with Fluentd for CLI logs, Prometheus for metrics, and Istio for service mesh monitoring and tracing. | Its BaaS integration uses Dapr and currently supports the pub/sub and bindings building blocks. |
| Languages | The documentation lists Node.js, Python, Go, Ruby, PHP, Bash, and custom container images as supported runtimes. | The sync-function examples cover Go, Node.js, Python, Java, and .NET. |
| License | Fission is open source under the Apache License. | OpenFunction is licensed under the Apache License, Version 2.0. |
| What it does | Fission is an open-source framework for running serverless functions on Kubernetes and mapping them to HTTP requests or other event triggers. | OpenFunction is a cloud-native, open-source Function as a Service platform for running functions without managing their underlying runtime environment and infrastructure. |
In their own words
OpenFunction
OpenFunction has no write-up on Specifiction yet; its figures are above.