HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
nzoschke
gofaas
Go2018–2019
nzoschke / gofaas

gofaas

A boilerplate Go and AWS Lambda app. Demonstrates an expert configuration of 10+ AWS services to support running Go functions-as-a-service (FaaS).

3Distinct people
27Mentions
1Explicit recommenders
801GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A boilerplate Go and AWS Lambda app. Demonstrates an expert configuration of 10+ AWS services to support running Go functions-as-a-service (FaaS).

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

This is my favorite feature of Go in Lambda. You cross compile a Linux binary, throw it in S3, and Lambda runs it on demand. It feels so good to skip over all the Docker tools,…

nzoschke used a recommendation phrase. 2 indexed comments match. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 6:28:55 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month27 dated mentions

Observed mentions: 2018-02-26 13:20:36 UTC to 2019-02-15 09:46:29 UTC.

02468102018-02-01 00:00:00 UTC to 2018-03-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 commentsFeb 20182018-03-01 00:00:00 UTC to 2018-04-01 00:00:00 UTC (exclusive): 10 mentions; 2 submissions, 8 comments2018-04-01 00:00:00 UTC to 2018-05-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2018-05-01 00:00:00 UTC to 2018-06-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2018-06-01 00:00:00 UTC to 2018-07-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2018-07-01 00:00:00 UTC to 2018-08-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2018-08-01 00:00:00 UTC to 2018-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsAug 20182018-09-01 00:00:00 UTC to 2018-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-10-01 00:00:00 UTC to 2018-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-11-01 00:00:00 UTC to 2018-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-12-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-01-01 00:00:00 UTC to 2019-02-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2019-02-01 00:00:00 UTC to 2019-03-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsFeb 2019

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Feb 20182018-02-01 00:00:00 UTC2018-03-01 00:00:00 UTC303
Mar 20182018-03-01 00:00:00 UTC2018-04-01 00:00:00 UTC1028
Apr 20182018-04-01 00:00:00 UTC2018-05-01 00:00:00 UTC211
May 20182018-05-01 00:00:00 UTC2018-06-01 00:00:00 UTC505
Jun 20182018-06-01 00:00:00 UTC2018-07-01 00:00:00 UTC202
Jul 20182018-07-01 00:00:00 UTC2018-08-01 00:00:00 UTC202
Aug 20182018-08-01 00:00:00 UTC2018-09-01 00:00:00 UTC000
Sep 20182018-09-01 00:00:00 UTC2018-10-01 00:00:00 UTC000
Oct 20182018-10-01 00:00:00 UTC2018-11-01 00:00:00 UTC000
Nov 20182018-11-01 00:00:00 UTC2018-12-01 00:00:00 UTC000
Dec 20182018-12-01 00:00:00 UTC2019-01-01 00:00:00 UTC000
Jan 20192019-01-01 00:00:00 UTC2019-02-01 00:00:00 UTC101
Feb 20192019-02-01 00:00:00 UTC2019-03-01 00:00:00 UTC202

What Hacker News says

10 sources
After the initial “cost” of figuring out how to configure the services, I’m finding the complexity far less than containers. Many concerns are removed from my application code and build and deploy systems by Lambda and API gateway. You just throw some zip files in S3 and you have a web service. No more image registry, container orchestration, load balancers, AMIs, autoscaling, etc. You also get to remove things code around CORS, auth, polling etc. from your app. I have a bunch of writing on how FaaS makes things easier here: https://github.com/nzoschke/gofaas
In From Express.js to AWS Lambda: Migrating Existing Node Apps to Serverless
Check out the Serverless Application Model (SAM): https://github.com/awslabs/serverless-application-model All of the manual configuration of API gateway vanishes because it builds up an implicit API gateway from your functions and event mapping config. You can see a boilerplate SAM config here: https://github.com/nzoschke/gofaas/blob/master/template.yml I'm hacking on CORS today and with SAM it's 2 lines of config to add the allowed origins and methods.
In AWS Lambda and .zip is a recipe for serverless success
nzoschke·Mar 18, 2018Recommendation phrase
Deploying .zip files is one of my favorite features of Lambda, particularly when writing Go apps. Docker always felt wrong with Go to me. Why do I need a local VM, a Linux build service, an image registry and servers with container orchestration to deploy Go software? I understand how all this helps with "legacy" Rails or Java apps, but why can't I just throw a Go binary somewhere to run it? Lambda is exactly this. I upload a cross-compiled .zip to S3 and everything else is taken care of. This was a big breakthrough for me, seeing a much simpler solution for deploys than all the container stuff. I've been building a boilerplate app that demonstrates just how little "stuff" is needed to run a Go service on Lambda: https://github.com/nzoschke/gofaas More thoughts about how .zip files make our lives easier is here: https://github.com/nzoschk
Read the rest
In AWS Lambda and .zip is a recipe for serverless success
I have been doing a lot of experiments with Go and Lambda and have an open source boilerplate app here: https://github.com/nzoschke/gofaas This benchmark leaves some room for improvement. With Lambda and X-ray you could really deep dive into where time is spent in a request. Here’s an example trace for a Golang function that does some actual work against KMS and DynamoDB: https://twitter.com/nzoschke/status/969598630033162240?s=20 One thing I found surprising about the Go support is that the ‘lambda.Start’ helper uses reflection to invoke your go func. This could contribute to some of the cold start time.
In Comparing AWS Lambda performance of Node.js, Python, Java, C# and Go
Golang for the API, running on Lambda. React or Vue for the UI. FaaS isn’t a fad, new systems built on an event based architecture are simpler, more cost effective, and scalable than the traditional application server approach. And the reactive programming pattern is easy and powerful and maps extremely well to modern UI needs. I have a boilerplate Go / Lambda app here: https://github.com/nzoschke/gofaas I use it with this excellent admin interface framework for CRUD tools: https://github.com/marmelab/admin-on-rest
In Ask HN: What stack would you use to build a CRUD web app in 2018?
I’m starting to find a FaaS architecture can remove complexity for the developer. The CRUD functions themselves are easy to write and test. Then everything else is handled by the infrastructure layer. Auth, security policies, rate limiting, request timeouts, autoscaling, logs, tracing, etc. With Rails the developer has to build a lot of this into the application layer. And the dev has to do more operations over time to maintain the app and database. I am working on a boilerplate app that demonstrates all the functionality you get from “serverless” and documents all of the things we no longer have to worry about: https://github.com/nzoschke/gofaas
In How we built Hamiltix.net for less than $1 a month on AWS

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.