If you have interest in both Go and FaaS (or Serverless), you’re probably aware that Go is now one of the supported languages for AWS Lambda:
When working with a small team (in my case, by myself alone) its really important to outsource as much work as possible to automation. Big companies have whole teams for testing and DevOps, but sometimes we don’t have…
In our last post we learned how to use Auth0 in a React application to authenticate users and allow them access to our Serverless application. That approach used JWT tokens produced by Auth0 and AWS…
We know how to deploy the application we created with the Serverless Framework in AWS. A CloudFormation script is created for us, which in turn will create our API Gateway…
Until now, we know how to start our serverless application in a local environment. We can test it and even save things in a local DynamoDB.
JavaScript is a great language: Provides flexibility and transparency. You can always now for sure what a variable contains without knowing what type it is because, well, there are no types.
On previous posts we talked about how to build unit tests for our Serverless application. While unit testing works great for TDD (Test Driven Development), in some moment we will want to run our Lambda application locally…
On our previous post we started to shape a sample Serverless project to decouple it’s business logic, allowing us to write effective tests for it.
In almost every software developer job interview I’ve seen, both interviewer and interviewed will tell an awful lie: They love TDD (Test Driven Development) and they never start a project without it. Cut to a few weeks later and they are sweating…
Java has Spring. Ruby has Rails. NodeJS has… well, NodeJS. What do we have for Serverless applications?
“The Serverless Framework allows you to deploy auto-scaling, pay-per-execution…