Go is a great language. I really like it. It’s super simple, statically typed, with a huge ecosystem. It makes you productive. Do you know what’s better than Go? An AWS Lambda function written in Go and deployed with Serverless Framework.
The experience of building Go services with Serverless Framework is not the best, though. Well, that’s pretty obvious because the framework is language-agnostic. Let me list some of the issues:
- Go is a compiled language, so you cannot simply run
serverless deploy functionafter each code change because you need to compile it. It requires an intermediate step making the dev experience a bit disturbed.
- Developers that are new to Go don’t know all the secrets of
go buildcommand. They tend to compile Go code without using addition flags causing the output file being larger than possible, which in turn causes the deployment process to take longer.
- When you define the function in
handlerproperty has to point to the compiled file, rather than to the source file. Again, not big of an issue, but it might be tricky for people starting with Go or/and Serverless Framework.
Usually, the solution is to have a
Makefile or some Bash script that will automate the compiling and deploying process. But there is a better way.
I really care about the developer experience, feedback loop, and about using well-tailored tools that make our work easier. That’s why I would like to introduce you to ⚡️ Serverless Framework Go Plugin!
The plugin solves all the aforementioned issues (and more!) and makes the development process seamless. Let see how it works.
Here is the minimal Go service:
service: example-service plugins: - serverless-go-plugin provider: name: aws runtime: go1.x functions: example: handler: ./functions/example/main.go memorySize: 128
Now, let’s see how it works:
If you're building a #golang service with ⚡️ @goserverless here is a plugin that will streamline your dev experience. It concurrently compiles your functions on-the-fly, so there is no need for custom build scripts or makefile.— Maciej Winnicki (@mthenw) February 6, 2020
🔌 https://t.co/uLxzw7Wyk8#serverless pic.twitter.com/xXdnHuni31
To sum up:
- no reference to the compiled file because the plugin compiles the handler on-the-fly (concurrently on all CPU cores)
- no need to set
packageconfiguration excluding all unnecessary files from the zipped payload. The plugin does that for you.
The plugin also supports
serverless deploy function and
serverless invoke local!