Today we’re proud to announce the release of Serverless V1.0-alpha2. Two weeks have passed since the very first release of our scheduled rolling release roadmap. Thanks to our great community we were able to jump into discussions around different topics regarding the vision for Serverless v1. With that help we were able to finish and release this second alpha of Serverless v1. To install the new version of Serverless run the following:
npm install -g serverless@alpha
Let’s take a quick look at what’s changed.
See #1486 and #1494 Cloud applications have underdone a shift over the past several years toward service orientation (e.g. “Microservices” or even “Nanoservices”). Starting with Serverless v1 we’ll also think in terms of services rather than a project (take a look here to read about services in Serverless v1). This is now also reflected in the way we package your project for the deployment to your cloud provider. Starting with alpha 2 your whole service will be zipped (instead of each function inside your service) and uploaded as a whole to your cloud provider. This approach has different upsides:
We’re also working on functionality to upload independent functions as well. If you have thoughts regarding that join the discussion here!
serverless create --name my-new-service --provider aws
This is an easy and simple way to create a basic scaffold for your new Serverless service. However we’ve discussed this way of creating a Serverless service with our community and saw a problem which arises when dealing with some of our core concepts for v1 which are
Starting with this release we’ll provide different templates for different use cases. For example, you can now generate a scaffold for your Node.js 4.3 service which runs on AWS by using our aws-nodejs template:
serverless create --template aws-nodejs
We’ve put together some basic templates here. More provider and language specific templates will follow soon.
See #1406 and #1453 Dealing with errors/problems in your application is always painful. We’ve overhauled our error reporting system to provide you with more detail on what went wrong and how you can resolve the problem. Additionally we’ve improved the overall UX to provide you a even better experience when working with our CLI.
functions: function1: handler: handler.handler events: - sns: topic
Take a look at the plugin code to get more in-depth information on how it works.
See #1599 and #1568 Our mission is to provide you the best tools and user experience when developing and dealing with Serverless infrastructures. Starting with the alpha 2 release we’ll gather anonymized usage data in order to determine where we can improve the user experience of the framework. We will always transparently communicate what data we collect and how we collect it. Additionally, we will NEVER collect any sensitive or private information. Please consult our documentation to get an always up to date reference regarding the tracking implementation. Keep in mind that this data is always anonymized and that you can always opt out of tracking if you wish!
We love our community! We’ve updated our CONTRIBUTING.md file to provide you with a better understand how you can get involved and contribute to Serverless.
Take a look at our upcoming beta release milestone to get an overview of what we're working on next. It will include:
We always appreciate feedback so feel free to comment on the issues or open up new ones!
We’ve successfully used Gitter in the past as a way to connect and interact with Serverless users from all over the world. In addition to that we’re also releasing our new Serverless forum alongside the alpha 2 release and would like everyone to join this platform to discuss the future of the Serverless framework and serverless application development in general! Create your account today and join the discussion. That’s it for now. We hope that you’ll like the alpha 2 and would love to hear your feedback about it!
Philipp Müns is a core developer at Serverless, Inc.