The Serverless Framework helps you develop and deploy serverless applications using Kubeless. It's a CLI that offers structure, automation and best practices out-of-the-box, allowing you to focus on building sophisticated, event-driven, serverless architectures, comprised of Functions and Events.
The Serverless Framework is different than other application frameworks because:
Here are the Serverless Framework's main concepts and how they pertain to Kubeless.
A Function is a Kubeless Function. It's an independent unit of deployment, like a microservice. It's merely code, deployed in the cloud, that is most often written to perform a single job such as:
You can perform multiple jobs in your code, but we don't recommend doing that without good reason. Separation of concerns is best and the Framework is designed to help you easily develop and deploy Functions, as well as manage lots of them.
Anything that triggers a Kubeless Event to execute is regarded by the Framework as an Event. Events are platform events on Kubeless such as:
A Service is the Serverless Framework's unit of organization (not to be confused with Kubernetes Services. You can think of it as a project file, though you can have multiple services for a single application. It's where you define your Functions and the Events that trigger them, all in one file by default entitled
serverless.js). It looks like this:
# serverless.yml service: users functions: # Your "Functions" usersCreate: handler: hello.hello # The code to call as a response to the event events: # The "Events" that trigger this function - http: path: /hello
When you deploy with the Framework by running
serverless deploy, everything in
serverless.yml (or the file specified with the
--config option) is deployed at once.