-
Notifications
You must be signed in to change notification settings - Fork 154
[Support Lambda Powertools]: WeSchool #2850
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. |
Hi @sav-valerio, thank you so much for opening this issue, and happy to hear that Powertools for AWS is helping WeSchool in their journey. I'll add the company name to the pages on Monday first thing. Thank you again! |
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 is now released under v2.7.0 version! |
Organization Name
WeSchool
Your Name
Saverio Valerio
Your current position
DevOps
(Optional) Company logo
https://static.weschool.com/logo.png
(Optional) Use case
At WeSchool our mission is to reinvent learning platforms and empower instructors & learners with a more inclusive, collaborative and engaging approach.
In 2023 we started to really take advantage of Serverless Computing and AWS Lambda for augmenting the feature set of our services.
We've been using pretty much the whole Powertools suite since then: mainly Logger, Metrics, Parameters and Tracer, but we will probably also have a look at the newer ones.
This really helped us starting to adopt quickly Lambda and focus on the business logic, instead of writing over and over again (or copying around between projects) utils.
Also using other Powertools for AWS Lambda languages?
The text was updated successfully, but these errors were encountered: