dazn-lambda-powertools
serverless
dazn-lambda-powertools | serverless | |
---|---|---|
4 | 24 | |
731 | 2,217 | |
0.3% | - | |
0.0 | 0.0 | |
10 months ago | 3 months ago | |
JavaScript | TypeScript | |
MIT License | 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.
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.
serverless
- Using Flask for API development
- Where can I find examples of cloud architectures ?
-
Confused around serverless trends and need opinion on the architecture.
I don't know any tutorials that cover all of these, but check out: https://cdkpatterns.com/ for 1) https://docs.aws.amazon.com/cdk/v2/guide/cdk_pipeline.html for 2) 3) and 5) https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/serverless-cdk-testing.html for 4)
-
Why are pulumi examples repo not showing good re-useable design patterns
I would like to see re-useable design patterns advocated similar to the terraform/terragrunt modules concepts. Encouraging pulumi.ComponentResource definitions multi environment structure, best practices. The cdk guys have something similar https://cdkpatterns.com/.
- Lambda best approach
-
Building a Flutter application (for Web) with AWS Lambda Function URL backend using AWS CDK Pipelines (written in Java)
While writing this post, the four stacks combined are 129 lines of source code. With the help of the CDK Constructs that are being used this translates to over 1k lines of code in CloudFormation. We are only using L2 constructs here – there is way more constructs available that you can use in the Constructs Hub and also a lot of guidance regarding the usage of CDK over at CDKPatterns.
-
In a serverless architecture, is it best to handle all API methods of a single entity in one lambda function with one API endpoint, or create an API endpoint for each and a lambda as a result?
I use the "Lambda-lith" pattern, primarily because I am using Rust and deploying via CI/CD (codepipeline).
-
Learning Lambda
Here is a read of common lambda design pattern https://github.com/cdk-patterns/serverless/blob/main/the-lambda-trilogy/README.md
- Makefile to manage containers ?
-
What Are AWS CDK Constructs, Stacks and How To Use Them
Level 3 constructs are opinionated units of reusable code which often deliver a service. Open source level 3 constructs are available from AWS Solutions Constructs - an extension to the CDK, CDK Patterns - a library of well-architected patterns, Construct Hub - a library of open-source constructs and some even come out of the box with the CDK - these are appended with 'patterns' to make them identifiable. Two examples are shown below:
What are some alternatives?
middy - 🛵 The stylish Node.js middleware engine for AWS Lambda 🛵
nx-serverless - 🚀 The Ultimate Monorepo Starter for Node.js Serverless Applications
powertools-lambda-typescript - Powertools is a developer toolkit to implement Serverless best practices and increase developer velocity.
lift - Expanding Serverless Framework beyond functions using the AWS CDK
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
terraform-aws-appsync - Terraform module to create AWS AWS AppSync resources 🇺🇦
logger-with-cache - An example of a logger for AWS Lambda which caches all messages
terraform-aws-next-js - Terraform module for building and deploying Next.js apps to AWS. Supports SSR (Lambda), Static (S3) and API (Lambda) pages.
Grant - OAuth Proxy
sst-start-demo - A simple SST app to demo the new `sst start` command
super-serverless-sample - Backend serverless que simula o sistema de votação do BBB
aws-sam-typescript-layers-example - Example project for developing AWS Lambda functions on TypeScript with all goodies: local development, tests, debugging, shared layers (3rd party and your own), and deploy.