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

2 sources
I really appreciate projects like this. It’s helpful for casual observers to understand all the pieces of the stack. You can get an immediate feel if the approach is right for you and your team. And it’s helpful for engineers to have examples to reference copy when implementing the patterns themselves. I’ve been working on project similar to this for go, gRPC and Envoy: https://github.com/nzoschke/gomesh My project doesn’t go into deployment or K8. If I needed to figure that out I’d look at the OP project. I also have a project that demonstrates Go and Lambda: https://github.com/nzoschke/gofaas If these help even a few engineers learn to be successful with the tools it’s a win.
In Sample cloud-native application with microservices
If you want to see what the “lock-in” actually looks like check out: https://github.com/nzoschke/gofaas It’s a boilerplate Go, Lambda, API gateway, dynamo, SNS, x-ray etc app. Personally I embrace the “lock-in”. This architecture faster, cheaper and more reliable than anything I’ve seen in my 15 years of web development. Most importantly it is less code. Most time is spent writing Go functions. A little time goes into configuring the infra but the patterns are simple. No time goes into building infra or a web framework. I think Go is the antidote to true lock-in. I have a ‘Notify’ function that uses SNS that I recently replaced with a Slack implementation. With well defined interfaces you can swap out DynamoDB for Mongo if you have to move. It is also easy to turn a function into a HTTP handler. There is a smooth path from function to con
Read the rest
tainer to server if the cost or performance of lambda doesn’t work. It’s hard or impossible to go the other way.
In “Lambda and serverless is one of the worst forms of proprietary lock-in” (2017)

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.