cdk-async-testing-example
dazn-lambda-powertools
cdk-async-testing-example | dazn-lambda-powertools | |
---|---|---|
3 | 4 | |
4 | 732 | |
- | 0.3% | |
0.0 | 0.0 | |
almost 2 years ago | 10 months ago | |
TypeScript | JavaScript | |
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
cdk-async-testing-example
-
First Look at Lambda Powertools TypeScript
If you want to see my instrumented code, it is available in this branch.
-
Cloud Driven Development - Episode #001
Example
-
Testing the Async Cloud with AWS CDK
Read enough already? Check out my source code.
dazn-lambda-powertools
-
First Look at Lambda Powertools TypeScript
I'm a big fan of TypeScript and in fact co-authored a book about it. I don't find myself using Java or Python much, so while I've been interested in Lambda Powertools, I never tried it out until now. Lambda Powertools TypeScript joins middy and DAZN Lambda Powertools in the Lambda tooling space for the Node.js runtime. Two things that differentiate Lambda Powertools TypeScript from comparable libraries are it is sponsored by AWS and it supports decorators.
-
Test Drive AWS Lambda Powertools for Typescript
The next natural step was to look at middleware such as Middy to decorate the main business logic, and allow these tasks to be defined once and used consistently. I remember listening to a Comic Relief talk about their Lambda wrapper back in 2019. Since then, I was introduced by Yan Cui to DAZN Lambda Powertools, which was the inspiration for this new project.
-
AWS Lambda logging best practices
You might be interested in the logger/correlation ID features of https://github.com/getndazn/dazn-lambda-powertools - been super useful for us so far.
-
Keep your CloudWatch bill under control when running AWS Lambda at scale
Nevertheless, log files are an important resource to debug problems and to get deeper insights into the behavior of a serverless system. Every logged detail might help to identify issues and to fix bugs and problems. Structured logging is important as log files can be analyzed much easier (e.g. with AWS CloudWatch Insights) which will save time and engineering costs. The dazn-lambda-powertools library provides a logger that supports structured logging for Node.js, the AWS Lambda Powertools offer the same for Python and Java.
What are some alternatives?
websocat - Command-line client for WebSockets, like netcat (or curl) for ws:// with advanced socat-like functions
middy - 🛵 The stylish Node.js middleware engine for AWS Lambda 🛵
aws-testing-library - Chai (https://chaijs.com) and Jest (https://jestjs.io/) assertions for testing services built with aws
powertools-lambda-typescript - Powertools is a developer toolkit to implement Serverless best practices and increase developer velocity.
cdk-eventbridge-socket - CDK construct that creates a WebSocket endpoint for you for any EventBridge rule you are interested in. (Built for debugging + testing )
dynamoDb-partiQL-javascript - This github repo contains the code examples and a getting started part to follow along with the blog article. It compares ways of querying and inserting data into dynamoDb using PartiQL vs using the Document Client using the AWS Javascript SDK
logger-with-cache - An example of a logger for AWS Lambda which caches all messages
aws-embedded-metrics-node - Amazon CloudWatch Embedded Metric Format Client Library
Grant - OAuth Proxy
powertools-lambda
super-serverless-sample - Backend serverless que simula o sistema de votação do BBB