Achieving the benefits of accelerated applications/services development while eliminating idle costs represent the foundational motivations of Fission, the open-source Functions as a Service (FaaS) serverless framework on Kubernetes.
Fission gives developers the advantage of creating useful applications/services without the need to know and implement the myriad number of steps it takes to deploy containers on Kubernetes.
Ideal for short-lived, stateless applications like DevOps automation or webhook implementation, Fission is also a good fit for creating small REST APIs e.g. backends of mobile applications and chatbot development.
Using Fission: Two Major Concepts To Learn
When it comes to Fission, a developer has to be familiar with two major concepts:
- Triggers – They are the bindings of an event to a function. For example, HTTP triggers map HTTP requests to functions or a particular message can map events on that message queue to functions.
- Functions – They can be written in various major languages including Node.js, Ruby, Python, Java and Go.
Why Serverless Framework on Kubernetes?
While Kubernetes based container orchestration provides uniformity to development and simplifies complex distributed systems, there are inherent difficulties for a newcomer e.g. building and push containers to a registry, know what registries to use, how to handle updates. All this adds to the complexity of using containers and Kubernetes. Fission eliminates or reduces repetitive tasks, allowing developers to innovate and speed up the development and deployment of new business functionality.
In addition, as more and more services are created, a certain minimum “fee” in terms of memory and CPU usage is being paid for the runtime resources used for running the services, even when the services are idle.
Fission, however, makes idle functions free by using a pool of pre-warmed containers that are always running. When function requests come in, Fission pulls from one of the warmed containers to load the function and send the event to that function. This allows the function to be free when idle but deliver fast response times when they are needed. By eliminating the costs for idle functions, Fission allows payment for the resources associated with the clusters to take place only in proportion to their utilization.
Learn more about Fission
If you’re ready to learn more about Fission, check out Platform9’s overview of Fission. For Fission webinars, news and blog posts, visit Fission Resources. Ready to delve in? Check out our GitHub project, Fission.io, and download Fission to start building your own serverless functions. Join the Fission community on Slack.
Hear about the compelling factors that drove me to create a serverless framework on Kubernetes and why FaaS heralds a new computing paradigm.
Latest posts by Soam Vasani (see all)
- Serverless Performance on a Budget - November 20, 2018
- NEW! Fission Announces New Features to Give Dev and Ops Confidence in the Production-Readiness of Serverless Applications on Kubernetes - October 16, 2018
- Serverless Operations: 6 Best Practices from Dev to Production - September 25, 2018