Serverless Best Practices for Team Leads
HTML-код
- Опубликовано: 28 окт 2024
- Hit SUBSCRIBE to say up to date on all things Serverless.
This webinar is for technical leaders - we'll go over everything you need to know to start off right when building a serverless team, and avoid costly mistakes that can derail your mission critical projects several months after you start scaling people and projects.
What we covered:
-How Serverless accelerates team velocity and eliminates infrastructure
-Organizing your serverless projects
-The Serverless Software Development Lifecycle
-Managing your shared and production AWS environments
-and... live Q&A!
-Presented by Gareth McCumskey - Developer Advocate @ Serverless
We want to hear what you think of this webinar! Let us know in the comments below!
For local development, how would we perform step-through/breakpoint debugging? Or is that just not possible with a serverless pattern??
Breakpoint debugging is one of the additional tools we developed to add onto our local development environments because its possible to do and is a nice improvement over all the other downsides of local development. However, In the serverless world, because we are testing directly on the same systems that will be running our application in production, this feature or tool set becomes harder to use. There have been efforts by Serverless and others to help bridge that gap. But ultimately we have found that the advantages serverless development brings to productivity and the amount of time saved testing directly against an exact replica of production outweighs any potential time lost by the lack of not having breakpoint debugging available.
@@Serverless I can foresee investment in that. If I can debug like I debug in production and practice that daily. When real production issues happen. Reading the same logs, etc will be second nature....
But that is indeed a hard transition, being in a field that uses live breakpoint debugging forever .... It is going to be a hard sale
Hmmmm of coz unit tested parts could use live debugging....