gofaas

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.

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

Static content served from S3 / CloudFront / ACM / Route 53. Lambda functions for APIs. I favor Vue for frontend and Go for backend but React and Node work just the same. https://github.com/nzoschke/gofaas/blob/master/docs/static-s...

You can set up a FaaS app just as fast as Heroku. I find it even more efficient, since Go, AWS SAM and Lambda offers dev/build/prod simplicity that Heroku never figured out. I open sourced and documented the stack that I use instead of Heroku here: https://github.com/nzoschke/gofaas

Not only is this stack free, it’s easy to develop and set up and operate. Here’s a boilerplate Go app that sets up this stack: https://github.com/nzoschke/gofaas

I have a boilerplate app / tutorial here: https://github.com/nzoschke/gofaas

If you anticipate needing more scale or control for your monolith, you will probably eventually need to learn about containers. Look at containers-as-a-service tech which includes Docker, Heroku's continer registry, ECS, and/or Kubernetes. If you anticipate building systems not as a monolith, look at Functions-as-a-Service. I'm in the FaaS camp for forward thinking work, and wrote up a bunch of my experiences here: https://github.com/nzoschke/gofaas

I do JWT token auth for apps as documented here: https://github.com/nzoschke/gofaas/blob/master/docs/security... In dev I run the same exact code and copy the JWT cookie from my production site. Both dev and prod have the same secret to validate the cookie.

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, config and services to build a Go app. I wrote up more details here: https://github.com/nzoschke/gofaas/blob/master/docs/dev-pack...

I make the go server/package the repo and add a web/ subdirectory for my static and dynamic JavaScript code, plus a little bit of Makefile glue. Here is a boilerplate Go Lambda app with a Node Lambda function and a static Vue app: https://github.com/nzoschke/gofaas

Nice guide. Going through the motions of setting up my first API Gateway and Lambda was eye opening to me. There are a ton of options in these two services — rate limiting, authorizers, concurrency, monitoring, etc. — that point to how much power you gain building an app like this. If you’d like to see an automated, infrastructure-as-code approach to setting up an API, check out my boilerplate app: https://github.com/nzoschke/gofaas

These lessons match muni experience building https://github.com/nzoschke/gofaas Except I opt for Golang and the Serverless Application Model (SAM). Go let’s you ditch even more stuff by cross compiling binaries. And SAM is a framework built by AWS and vastly simplifies the config files.

AWS, particularly Lambda, step functions and budgets. The business is a marketplace addon. Lambda functions handle the webhooks to add, upgrade or remove the addon. Step functions handle guiding new users through onboarding, by sending email reminders automatically re-configuring the service based on customer actions. Budgets make sure a customer is not using more resources than they are paying for, and send email alerts to me and customers at various usage amounts. I have extracted a lot of my AWS and Lambda software into an open source boilerplate app: https://github.com/nzoschke/gofaas It's amazing how little code and operations this business requires!

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