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 container to server if the cost or performance of lambda doesn’t work. It’s hard or impossible to go the other way.
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 container to server if the cost or performance of lambda doesn’t work. It’s hard or impossible to go the other way.