Serverless computing: Difference between revisions

Revision as of 13:09, 10 October 2024

Revision as of 21:52, 14 October 2024

Line 92:

Following [[DevSecOps]] practices can help one to use and to secure serverless technologies 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 serverless 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, serverless applications should to be tested mainly for their integrations, and arguably, unit tests should be used only if there is a complex business logic. Also, to make debugging and implementation of serverless applications easier, developers should use [[Orchestration (computing)|orchestration]] within the [[Domain-driven design|bounded context]] of a [[microservice]], and should use [[Service choreography|choreography]] between the bounded-contexts.<ref name=":0">{{Cite book |last=Cui |first=Yan |title=Serverless Architectures on AWS |publisher=Manning |year=2020 |isbn=978-1617295423 |edition=2nd}}</ref>

According to Yan Cui, ephemeral resources should be kept together to achieve a high [[Cohesion (computer science)|cohesion]]. However, shared resources that have a long spin-up time (e.g. [[AWS RDS]] cluster) and landing zone should have their own separate r[[Repository (version control)|epositoryrepository]], [[deployment pipeline]] and stack. <ref name=":0" />

== Uses/functions ==