It has started as an organic response to the accidental complexity of many existing tools used by serverless developers.
This is not an official AWS or HashiCorp product, and not to be confused with the Serverless Framework.
Most of the existing solutions require you to become a Serverless Superhero to get things done!
Developers and DevOps/Cloud engineers have to deal with several types of tools:
Developers and DevOps/Cloud engineers manage different infrastructure services differently (for various reasons).
For example, serverless resources (API Gateways, AWS Lambda functions) are managed as part of the application framework, and traditional resources (VPC, IAM roles, S3 buckets) - using infrastructure management tools.
Use a single tool that was created to manage infrastructure as code – Terraform – for all of your infrastructure resources.
Developers like to have control of their environment as code. They also prefer running integration tests often before lengthy deployment cycles kick off.
Have all infrastructure resources described as configuration files. This allows developers to spin up and tear down complete environments required for their work easily.
Having interaction with real services is often slower than running everything locally (eg, using localstack) but interaction with real services gives the most accurate feedback regarding how AWS services work.
Some of the existing solutions support plugins that extend the functionality of the framework and to simplify the usage of infrastructure services.
By relying on open-source Terraform AWS modules that have been developed over the course of several years by Betajob in partnership with our huge community, you get to build your serverless project on top of verified, reusable components.
Please, contact Betajob if you want to sponsor the development of missing modules or features.
The challenges listed above apply to the Serverless Framework, too. One of the biggest for us at Betajob was infrastructure fragmentation between CloudFormation and Terraform.
serverless.tf does not restrict you from setting up your CI/CD workflow, which suits your needs, but it gives you the ways to control building, testing, deployments steps as code.
All of them. serverless.tf does not restrict you there, but it gives you a way to build, package, and deploy your code in a standardized way.
As far as we know, only we at Betajob are using serverless.tf framework, but Terraform AWS modules used by the framework are used by thousands of companies worldwide. We are going to continue developing Terraform modules we need for us and our clients.
AWS only (for now).
Yes, please reach out to Betajob.
We don't know this for sure yet, and we are going to find this out as more people use the framework and give feedback.
We develop reusable solutions for our customers, or when we need them ourselves. Reach out to us if you want to discuss this or to sponsor the development of missing functionality.
Got any questions? Or want to sponsor development? Don't hesitate to reach out.