-
Notifications
You must be signed in to change notification settings - Fork 154
[Support Powertools for AWS Lambda (TypeScript)]: Alma Media #2020
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Thanks for opening your first issue here! We'll come back to you as soon as we can. |
Hey @aripalo thank you so much for adding your support, it means a lot! I will add it to the docs right away! |
Happy to help spreading the word! |
Oops… I accidentally inflated those numbers 😅 I counted some of the lock-files referencing powertools into the mix, but the actual number is about |
This issue is now closed. Please be mindful that future comments are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so. |
This number is from the future 😎 |
Yeah 😎 And to be honest, at this rate, not from too far future either. Pretty much all new serverless projects are using Powertools by default and I constantly see PRs adding Powertools to existing projects. |
Organization Name
Alma Media
Your Name
Ari Palo
Your current position
Lead Technologist
(Optional) Company logo
https://www.almamedia.fi/wp-content/themes/almamedia/dist/images/main-logo.svg
(Optional) Use case
Alma Media has been heavily utilizing AWS Serverless technologies since 2016 with AWS Lambda at its core. Powertools have greatly simplified how our developers are able to instrument observability and implement best practices into the services they build. As of today (February 2024), over
7040 different projects – a number that keeps growing – depend on AWS Powertools.(* corrected a wrong number of projects 😅 see #2020 (comment) )
Also using other Powertools for AWS Lambda languages?
The text was updated successfully, but these errors were encountered: