AWS Lambda: Difference between revisions

Content deleted Content added
Best practices: Correct grammar
No edit summary
Line 23:
==Best practices==
Following [[DevSecOps]] practices can help end-users to use and secure Lambda-based applications more effectively. <ref>{{Cite book |last=Katzer |first=Jason |title=Learning Serverless: Design, Develop, and Deploy with Confidence |publisher=O'Reilly Media |year=2020 |isbn=978-1492057017}}</ref> In Lambda-based applications, the line between the infrastructure and business logic is blurred and the apps are usually spread across various services. According to Yan Cui, to get the most value from testing efforts, Lambda-based applications should be tested mainly for their integrations, and unit tests should be used only if there is a complex business logic. Also, to make debugging and implementation of Lambda-based easier, developers should use [[Orchestration (computing)|orchestration]] within the [[Domain-driven design|bounded context]] of a [[Microservices|microservice]], and should use [[Service choreography|choreography]] between the bounded-contexts.<ref>{{Cite book |last=Cui |first=Yan |title=Serverless Architectures on AWS |publisher=Manning |year=2020 |isbn=978-1617295423 |edition=2nd}}</ref>
 
==Helper Tools==
Lambda Live Debugger is an open/source tools that helps you debug your AWS Lambda functions from your computer, even though they are deployed in the cloud. It supports AWS CDK v2, Serverless Framework v3, AWS Serverless Application Model (SAM) and Terraform. <ref>{{Cite web |title=Lambda Live Debugger |url=https://github.com/ServerlessLife/lambda-live-debugger |url-status=live}}</ref>
 
==See also==