Well everyone, we now have a few different product updates to give. We're welcoming Serverless Components and Event Gateway into the product updates family!
We are combining all of these into Serverless Platform updates.
Jump straight into the section you want to read about:
The new components release contains a bunch of goodies.
In version 0.3, you can now reference a component type using a url as a source. This allows for reusable components by uploading them to a URL first, giving teams a way to share components.
Alongside the ability to use Components from a url, we have also added a package command. This command will pack up a component directory into a zip for reuse.
This feature gives developers a way of declaring which version of Components core their component is compatible with. If a component is included that is incompatible with the current version of core, an error is thrown.
We've added methods for using the components package programmatically. The documentation for these new methods can be found here.
We've moved to using babel compilation for components, so the components package now supports version node 4 and greater.
Framework v1.27 introduces Fn support, fixes for the variables system, and support for AWS GovCloud and China regions.
You can find a complete list of all the updates in the CHANGELOG.md file.
The Fn Project is an open-source, container-native serverless platform that runs on any cloud or on-prem. And now there is an integration with the Serverless Framework.
Read here for more details and some examples.
We introduced several improvements and fixes, including pre-population of service and region values, a "PromiseTracker" class, and more.
Read up on the whole list of changes!
Just what it says on the tin. Check it out here!
This release contains lots of hard work from our beloved community, and wouldn't have been possible without passionate people who decided to spend their time contributing back to make the Serverless Framework better.
Huge round of applause to all of the contributors who submitted changes for this release! 👏
The Event Gateway plugin for the Serverless Framework makes it dead simple to deploy your Lambda functions with Event Gateway.
The plugin enables you to:
The Cloud Native Computing Foundation (CNCF) has been working on CloudEvents, a specification for describing event data in a common way across providers. At Serverless, we've taken a leading role in this effort; we believe strongly in the importance of standards and interoperability in this new event-driven world.
As such, Event Gateway CloudEvents-compatible. All functions receive a CloudEvents payload describing the event received.
Connectors let you Write Less Code in the true serverless way. Configuration is better than code wherever possible.
In that spirit, Connectors in Event Gateway are bits of logic which take your event and send it to another system—Firehose, Kinesis, or SQS for instance—without having to write the boilerplate integration code into a Lambda function.
If there's something you want to change about the Serverless Framework, Event Gateway or Components, open an Issue! We even have a quick & easy guide on contributing to Serverless open source projects.
PR reviews are also highly welcomed, as they greatly speed up the time-to-merge.
The Serverless Examples Repository is an excellent resource if you want to explore some real world examples, or learn more about the Serverless Framework and serverless architectures in general.
Serverless provides a completely customizable and pluggable codebase. Our community has written a vast amount of awesome plugins you can use to further enhance the capabilities of the Framework. You can find the full list at our Serverless Plugins Repository.
Don't hestitate to open up a PR over there if you have a new Framework plugin to submit!
To get started, pop open your terminal & run
npm install serverless -g
Join 12,000+ other serverless devs & keep up to speed on the latest serverless trends