[{"data":1,"prerenderedAt":83},["ShallowReactive",2],{"explore-svs315":3},{"id":4,"title":5,"YouTubeChannelID":6,"banner":6,"contributors":7,"description":6,"extension":9,"introBox":10,"meta":13,"pdf":6,"resources":14,"stem":81,"type":6,"video":6,"videos":6,"__hash__":82},"explore\u002Fexplore\u002Fsvs315.json","SVS315: Best Practices for Growing a Serverless Application",null,[8],"content\u002Fcontributors\u002Fbenjamin-smith.json","json",{"headline":11,"text":12},"Resources for SVS315: Best practices for growing a serverless application","So your serverless proof of concept became an MVP (minimum viable product) and launched to your customers with great success. Now you need to grow and expand that serverless application in functionality and complexity to deal with increased business needs. How should you think about tackling challenges such as when to break apart functions, create new APIs, and create new AWS Lambda “microservices” to overcome organizational challenges? How can you use features of AWS to help facilitate this? In this session, learn how to tackle the real scaling challenges, not getting your application to handle more requests, but getting your team to scale its development and do less while seeing more of the benefits of serverless. ",{},{"left":15,"right":44},[16,23,29,34,39],{"headline":17,"subheading":18,"text":19,"button":20},"Challenge 1: The Lambda-lith","The serverless LAMP stack part 6: From MVC to serverless microservices","In this post I show how to move from using a single Lambda function as scalable web host with an MVC framework, to a decoupled microservice model.",{"text":21,"link":22},"Read","https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fcompute\u002Fthe-serverless-lamp-stack-part-6-from-mvc-to-serverless-microservices\u002F",{"headline":24,"subheading":25,"text":26,"button":27},"Challenge 2: The mono-repo","Best practices for organizing larger serverless applications","This blog post provides recommendations for designing and managing code repositories in larger serverless projects, and best practices for deploying releases of production systems.",{"text":21,"link":28},"https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fcompute\u002Fbest-practices-for-organizing-larger-serverless-applications\u002F",{"headline":30,"subheading":31,"text":32,"button":33},"Challenge 3: Enforcing security best practices","Castle-and-moat vs Zero trust","Build micro-perimeters to enforce strict verification of every person or service.",{"text":21,"link":22},{"subheading":35,"text":36,"button":37},"Delegate permission management to developers by using IAM permissions boundaries","As your organization grows, you might want to allow trusted employees to configure and manage IAM permissions to help your organization scale permission management and move workloads to AWS faster. ",{"text":21,"link":38},"https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fsecurity\u002Fdelegate-permission-management-to-developers-using-iam-permissions-boundaries\u002F",{"subheading":40,"text":41,"button":42},"Using Lambda layers to simplify your development process","This post explains how layers work, and how you can build and include layers in your own applications.",{"text":21,"link":43},"https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fcompute\u002Fusing-lambda-layers-to-simplify-your-development-process\u002F",[45,47,52,57,62,67],{"headline":46},"Challenge 4: Managing multiple AWS accounts",{"subheading":48,"text":49,"button":50},"Cross-account deployment using CodePipeline","Use a single pipeline to deploy a microservice into multiple accounts; for example, a microservice must be deployed to environments such as DEV, QA, and PROD, all in separate accounts.",{"text":21,"link":51},"https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fcompute\u002Fmanaging-cross-account-serverless-microservices\u002F#attachment_3937",{"subheading":53,"text":54,"button":55},"Cross-account lookup","During deployment, a resource deployed into one AWS account may need to refer to a resource deployed in another AWS account.",{"text":21,"link":56},"https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fcompute\u002Fmanaging-cross-account-serverless-microservices",{"subheading":58,"text":59,"button":60},"Cross-account communication","Microservices executing in one AWS account may need to communicate with microservices executing in another AWS account.",{"text":21,"link":61},"https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fcompute\u002Fmanaging-cross-account-serverless-microservices\u002F#code-toolbar",{"subheading":63,"text":64,"button":65},"Simplifying cross-account access with Amazon EventBridge resource policies","This blog post shows you how to use EventBridge resource policies to publish events and create rules on event buses in another account.",{"text":21,"link":66},"https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fcompute\u002Fsimplifying-cross-account-access-with-amazon-eventbridge-resource-policies\u002F",{"headline":68,"subheading":69,"text":70,"bullets":71},"Resources for growing your serverless applications","Code examples","Use these code examples to help implement some of the best practices described in this session",[72,75,78],{"text":73,"link":74},"From Lambdalith MVC to microservices","https:\u002F\u002Fgithub.com\u002Faws-samples\u002Fphp-examples-for-aws-lambda\u002Ftree\u002Fmaster\u002F0.6-MVC-to-microservice",{"text":76,"link":77},"AWS cross account serverless deployment","https:\u002F\u002Fgithub.com\u002Faws-samples\u002Faws-cross-account-serverless-microservices",{"text":79,"link":80},"Amazon EventBridge resource policy samples","https:\u002F\u002Fgithub.com\u002Faws-samples\u002Famazon-eventbridge-resource-policy-samples","explore\u002Fsvs315","suXI1jSBwITNPLC0GqP0H479frlwJ8HXbl22M_yt9pk",1792665262438]