Learn FISSION with Real Code Examples

Fission runs on top of Kubernetes, leveraging its orchestration and scaling capabilities.

Developers write functions in multiple languages (Go, Python, Node.js, etc.) and deploy them without container management.

Supports HTTP triggers, message queues, cron schedules, and Kubernetes events.

Provides automatic scaling and load balancing for functions based on demand.

Designed for microservices, event-driven workflows, and cloud-native serverless applications.

Function-as-a-Service (FaaS) model

HTTP, message queue, and cron triggers

Pre-built language runtimes (Go, Python, Node.js, .NET, Ruby)

Cold-start optimization with pool manager

Kubernetes-native deployment and management

Function - the deployed unit of code

Trigger - event source that invokes functions

Environment - language runtime for functions

Pool Manager - pre-warms pods to reduce cold starts

Router - directs requests/events to correct function

functions/ - function source code

environments/ - runtime definitions

triggers/ - event sources and schedules

config/ - Fission configurations

deployment scripts - optional Helm or YAML files

Write function code in supported language

Create environment for the function runtime

Deploy function with `fission fn create`

Bind triggers to the function (HTTP, cron, MQ, etc.)

Test function via `fission fn test` or HTTP endpoint

Beginner: single HTTP-triggered function

Intermediate: cron job or message queue trigger

Advanced: multi-language function pipeline

Expert: event-driven microservices with multiple triggers

Auditor: optimize cold-start and scaling performance

Fission vs AWS Lambda: Fission runs on Kubernetes, Lambda is cloud-managed

Fission vs OpenFaaS: Both serverless on Kubernetes, Fission emphasizes triggers and CLI simplicity

Fission vs Knative: Knative provides full serverless platform, Fission focuses on lightweight FaaS

Fission vs Micronaut: Micronaut is full-stack framework, Fission is function-only serverless

Fission vs Spring Boot: Spring Boot is monolithic/microservice framework, Fission is serverless functions

2017 – Fission initial release by Platform9

2018 – Added pool manager for cold-start optimization

2019 – Added multiple language runtimes

2020 – Improved Kubernetes integration and triggers

2021–2025 – Continuous improvements, CI/CD, monitoring, and community growth

Function - unit of serverless code

Trigger - event source invoking functions

Environment - runtime for functions

Pool Manager - pre-warms pods to reduce cold starts

Router - directs events/requests to functions