3 ms·

What does serverless offer over just vanilla lambda functions?

by Jsharm 8y ago

sewercake 8y ago
well, for one, it provides a common api across a host of different cloud providers (aws, azure, google cloud)
nathan_f77 8y ago
I don't know too much about it, but it's a framework for managing your lambda functions, and it makes it really easy to deploy them to a cloud provider. You could also use Terraform, CloudFormation templates, or write your own shell scripts using the AWS CLI. But serverless does everything for you, and I always prefer to use opinionated tools that don't require too much configuration.
- guitarbill 8y ago
  With serverless, you'll probably end up writing a CloudFormation template snippets to provision resources to support the Lambda anyway (it's just in the serverless YAML file). But it does make deployment easier. A good example is macOS + Python. If you have C extensions (such as LXML or crypto libs, etc.), you'll want to build the dependencies inside a Linux environment. serverless has a plugin that can use docker to build and package dependencies. For reasons I can't put my finger on, I'm not a huge fan of serverless. Maybe the npm focus? But it seems like the best tool out there for Lambdas. Unless you're use-case is narrower, then something like Zappa might make sense.
b3arlythere 8y ago
It offers a file driven framework rather than just a web-editor. With that comes many different strengths including plugins, importing libs/modules to the deployables, as well as components. It also has a variety of examples to work with.
brnkrygs 8y ago
We've been heavy users of the Serverless Framework on AWS for the last 2 years. In short, its a template generator for the resource management system of your cloud provider of choice (supporting AWS, Azure, Google, and a few others), with some deployment management CLI tools mixed in. In our case, it generates boilerplate CloudFormation (since we're in AWS most of the time) based on the "common cases" of how Lambda and API Gateway work together - including the necessary IAM and CloudWatch templates, and wraps the AWS CLI with with deployment commands, which we leverage in our CI/CD pipelines. It's a great way to get started on small, or even medium-sized projects. For larger systems you'll probably need more direct control of your CloudFormation templates.
kennu 8y ago
In my experience, if you don’t use Serverless Framework, you will end up writing the same functionality yourself as custom deployment scripts, which will not be as stable, extensible and well documented. There are some alternatives in the Amazon ecosystem, such as AWS SAM and AWS CDK, but they are only now approaching the maturity level of SF and don’t have the same amount of plugins for various use cases.

What does serverless offer over just vanilla lambda functions?

by Jsharm 8y ago

What does serverless offer over just vanilla lambda functions?

sewercake 8y ago

well, for one, it provides a common api across a host of different cloud providers (aws, azure, google cloud)

nathan_f77 8y ago

I don't know too much about it, but it's a framework for managing your lambda functions, and it makes it really easy to deploy them to a cloud provider. You could also use Terraform, CloudFormation templates, or write your own shell scripts using the AWS CLI. But serverless does everything for you, and I always prefer to use opinionated tools that don't require too much configuration.

guitarbill 8y ago
With serverless, you'll probably end up writing a CloudFormation template snippets to provision resources to support the Lambda anyway (it's just in the serverless YAML file). But it does make deployment easier. A good example is macOS + Python. If you have C extensions (such as LXML or crypto libs, etc.), you'll want to build the dependencies inside a Linux environment. serverless has a plugin that can use docker to build and package dependencies. For reasons I can't put my finger on, I'm not a huge fan of serverless. Maybe the npm focus? But it seems like the best tool out there for Lambdas. Unless you're use-case is narrower, then something like Zappa might make sense.

b3arlythere 8y ago

It offers a file driven framework rather than just a web-editor. With that comes many different strengths including plugins, importing libs/modules to the deployables, as well as components. It also has a variety of examples to work with.

brnkrygs 8y ago

We've been heavy users of the Serverless Framework on AWS for the last 2 years. In short, its a template generator for the resource management system of your cloud provider of choice (supporting AWS, Azure, Google, and a few others), with some deployment management CLI tools mixed in. In our case, it generates boilerplate CloudFormation (since we're in AWS most of the time) based on the "common cases" of how Lambda and API Gateway work together - including the necessary IAM and CloudWatch templates, and wraps the AWS CLI with with deployment commands, which we leverage in our CI/CD pipelines. It's a great way to get started on small, or even medium-sized projects. For larger systems you'll probably need more direct control of your CloudFormation templates.

kennu 8y ago

In my experience, if you don’t use Serverless Framework, you will end up writing the same functionality yourself as custom deployment scripts, which will not be as stable, extensible and well documented. There are some alternatives in the Amazon ecosystem, such as AWS SAM and AWS CDK, but they are only now approaching the maturity level of SF and don’t have the same amount of plugins for various use cases.