Amazon just recently announced native Golang support for AWS Lambda. Together with the Serverless Application Model (SAM) you can easily deploy your Golang code and create an HTTP interface using Amazon API Gateway.
I created an example project on GitHub with multiple binaries that are deployed using CircleCI and the AWS Command-Line interface. Thanks to the Serverless Application Model the needed CloudFormation template is minimal, compared to creating all resources individually:
AWSTemplateFormatVersion: 2010-09-09 Transform: AWS::Serverless-2016-10-31 Resources: People: Type: AWS::Serverless::Function Properties: Handler: dist/handler/people Runtime: go1.x Tracing: Active Events: GetEvent: Type: Api Properties: Path: /people Method: get
You can easily notice, the Serverless Application Model is heavily influenced by the serverless project. Together with improved AWS performance, using Golang, AWS Lambda, and SAM seem to create a perfect setup to deploy serverless applications.
Let me be honest with you: GraphQL is the shit! Once you use GraphQL, you will never want to use anything else again. The same is true for a working and maintainable serverless FaaS infrastructure. Combine both technologies to run a genuinely serverless GraphQL API using AWS AppSync and Lambda resolvers.1501 words, posted on June 17
Amazon recently announced CloudFormation support for AppSync and all its features. Together with the Serverless Application Model it’s now dead simple to deploy a GraphQL API and custom Lambda resolvers without using the API at all. The GraphQL RSS Proxy example project is a serverless GraphQL API using AppSync, with an AWS Lambda function as a custom Query Resolver writting in Go.714 words, posted on May 30
Do you use GitHub to manage your software projects and Slack for communication? With GitHub Webhooks and a simple AWS Lambda function, you can notify Slack channels about new releases of your projects.540 words, posted on February 24