Serverless V1.0 Beta 1

Aug 3, 2016

announcement_v1beta1 It’s been two weeks since our Serverless V1.0-alpha.2 release. Lots of valuable feedback and suggestions were submitted and discussed since then. Thanks to the help of our great community we’re proud to announce our first beta release today: Serverless V1.0-beta.1 Let’s take a closer look what has changed / is new.

Multi language support

Up until now Serverless only supported Node.js as a runtime and JavaScript as the corresponding programming language. In Serverless v1.0-Beta.1 you’ll be able to use Node.js, Python 2.7 or Java (via Gradle or Maven) as a runtime for your projects. Using these new runtimes is easy and you’re already familiar with how to create a service through the new runtimes. Just use the create command with the aws-java-maven template parameter to e.g. create a new Java (via Maven) based service on AWS:

serverless create --template aws-java-maven

To see a list of available templates and options for creating a new service run

serverless create --help

You can also change the runtime of existing services by updating the provider runtime attribute in serverless.yml like this:

  name: aws
  runtime: java8

Take a look at the service templates docs to see how you can use the other templates. A big “Thank you!” goes out to Ilya Shindyapin (@license2e) who took the time to get Java support into Serverless. See #1247, #1552 and #1554 (Python support), #1246, #1553 and #1672 (Java support)

API Gateway updates

The API Gateway event source is one of the most used and most complex event sources out there. There are many things one can configure. Take a look at the API Gateway documentation to see how you can use all those new settings. See #1594 and #1620 (Custom Authorizers), #1598, #1603 and #1666 (Proxy settings), #1595 and #1636 (API keys)

VPC support

Sometimes you want to configure your lambda functions so that they can be operated in a VPC environment. This feature was also added to the beta 1 release! Take a look at the documentation to see how you can setup the corresponding configuration parameters so that your lambda function can be operated in a VPC environment. See #1489 and #1705

Developer plugins / tooling

Our mission for the Serverless framework is to provide an easy to use, yet powerful tool which helps you as a developer while working on your Serverless services and projects. Tedious tasks / configurations should be abstracted away so that you can focus on your code and be more productive. A feature rich toolset which supports you in your day to day development is vital here. Because of that we’ve started the discussion with the community what kind of developer tooling plugins are of interest and needed to be more productive while working with Serverless. V1.0-Beta.1 includes the following plugins which will help you develop your Serverless services:

  1. Info plugin Prints out what resources are deployed to AWS
  2. Logs plugin See all your functions logs and browse through them on your console (supports tailing as well)
  3. Single function deployment Blazing fast way to deploy a single function of your service (e.g. to test recent changes on a cloud provider infrastructure)

Big thank you to Benny Bauer (@bennybauer) who implemented the whole info plugin! What plugins do you need for your daily work? Any ideas or thoughts? Please let us know and jump into the discussion here. See #1582 (main discussion), #1468, #1590 and #1708 (info plugin), #1654 and #1691 (logs plugin), #1652 and #1696 (single function deployment plugin)

.yaml and .yml support

YAMLs official file extension is .yaml which we’ve supported right from the beginning. However .yml is used often due to its brevity. Serverless V1.0-Beta.1 will now support both file extensions (.yaml and .yml). The default Serverless will choose (e.g. upon service creation) is .yml and we recommend that you switch to this file extension. See #1168, #1342 and #1681

Documentation updates, bug fixes and v1 as the main version

The documentation is a key piece for every software project. Without it (or with poor documentation) developers won’t be able to use the product and can’t work with it. In this beta 1 release we’ve updated our documentation with new examples, sections for new functionality and many different minor fixes. We would like to hear your feedback on our docs. What do you think is missing? Should we consider another structure? Please chime in on this issue and let us know what you think! Additional to the documentation updates we’ve also fixed a bunch of nasty bugs so that Serverless is way more stable and reliable. That’s why we’ve decided to merge the v1.0 branch into the master branch and mark v0 as deprecated. Serverless v1 is now the go to version when you’re about to work on a new project or want to get started with Serverless.

A big thanks to our contributors!

We’ve seen a dramatic increase in contributions the past months and would like to use this blog post to say thank you to the community for all the work they’ve done to make Serverless great! Contributing to Serverless is not hard at all! We’ve just introduced the “easy-pick” label which shows what issues are easy for a first time contribution. Other than that we’re always happy if you discuss with us in the issues or pull requests. This blog post might also be interesting for you as it shows you what the usual workflow for open source contributions looks like. Here’s a list of all people who have contributed code for the beta 1 release (in no particular order):

There are way more awesome people who have helped by jumping in on issue discussions, pull requests, discussions on Gitter or the Serverless forum. Thanks everyone!


Take a look at our v1.0.0-beta.1 milestone to get an overview of all changes in Beta 1.

What’s next

The next release will be the second beta release and is scheduled for mid of August. It will include the following:

  • Improved stage / region / env variable and secrets support
  • Better documentation and onboarding for new users
  • Integration with Lambda versions / aliases
  • Event integration test repository (to test all the event sources)
  • Community plugin repository (a repository for community plugins)

We would like to hear your feedback about this and have created an issue where we’ll discuss this milestone goals (you can find all milestone discussion issues with the help of the recently introduced “milestone-discussion” label). We’ve already created the beta 2 milestone and added corresponding issues and pull requests. It would be great if you could give us some feedback on the things we’re about to implement so feel free to comment on the issues or open up new ones! Only a few weeks are left when we’ll finally release Serverless v1 in fall 2016

Join the discussion in our Serverless forum

GitHub is a great place to talk and discuss technical topics. For all other, more general topics about the Serverless framework, the serverless architecture, support questions, etc. you might want to look into our Serverless forum which is available at: Create your account today and join the discussion. That’s it for now. We hope that you’re as excited as we are and like the first beta release. We would like to hear your feedback and future features you want to see in the Framework. You can find us on Twitter, GitHub and our Forum.

Subscribe to our newsletter to get the latest product updates, tips, and best practices!

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.