Lambda is where most of my AWS work happens. It’s the default I reach for when a system needs to respond to requests or events without anyone having to own a server, and I’ve built production Lambda systems on contract at six companies.
How I build with Lambda
The functions are only half of it. A Lambda system is really the wiring between them — queues, topics, event buses, streams — and that’s where the decisions that matter actually live. I define all of it as code in CloudFormation, SAM or Terraform, so an environment can be rebuilt or changed without anyone guessing.
The other half is testing. Lambda systems are awkward to test well, which is why I wrote @kensio/yulin, an open source package that simulates Lambda and the services around it in-process. One fast test can then cover a Lambda writing to a queue that triggers another Lambda — which is the behaviour you actually care about.
Both of those exist for the same reason: to keep a system changeable late in a project, when the schedule has the least room in it.
What I can do for you
- Build a new Lambda-based application or API, with the infrastructure and deployment pipeline that go around it.
- Take on an existing Lambda estate and get it back under control, in code and under test.
- Work out whether Lambda is actually the right fit for what you’re building, and say so plainly where containers would serve you better.
Lambda work I’ve delivered
- Fanalysis — Lambda alongside ECS, API Gateway, DynamoDB and Rekognition.
- Octopus Energy — Lambda with SAM, CloudFormation, DynamoDB, SNS and SQS.
- HOA Mailers — Lambda and RDS, deployed with AWS SAM.
Hire a freelance AWS Lambda developer
Contact me about your Lambda project, whether that’s building something new, taking on an existing system, or getting a serverless architecture back under control.
I write Lambda functions mainly in TypeScript and Python, and I deliver complete MVPs built this way.