The lines between static and dynamic content are blurred, and it’s more difficult than ever to choose the right technologies for your requirements and budget. John Chapin takes you on a step-by-step journey from hosting static content on AWS S3 to deploying dynamic, complex business logic mere milliseconds away from your users with AWS CloudFront, Lambda@Edge, and more. Along the way, John explores complementary features such as custom DNS, SSL encryption, and metrics and logging.
In addition to those technologies, John addresses operational concerns like deployment and updates, cost control (especially given the scalability of the technology involved), and security from both an application and an AWS perspective. John concludes by detailing some of the idiosyncrasies of the approach, including the inherent limitations of the Lambda@Edge execution environment. You’ll leave with functioning, parameterized infrastructure templates to build your own serverless content stack.
While the examples will be primarily oriented around AWS, the concepts are applicable to other cloud platforms.
John Chapin is a cofounder of Symphonia, an expert consultancy based in New York City that helps companies of all sizes use serverless and cloud technology to deliver value quickly and effectively. Along with Symphonia cofounder Mike Roberts, John authored the recent O’Reilly report, What Is Serverless? His and Mike’s highly regarded talks and workshops are regularly featured at conferences such as Software Architecture Conference, Velocity, OSCON, QCon, ServerlessConf, and AWS re:Invent. John can be reached at firstname.lastname@example.org.
Help us make this conference the best it can be for you. Have questions you'd like this speaker to address? Suggestions for issues that deserve extra attention? Feedback that you'd like to share with the speaker and other attendees?
Join the conversation here (requires login)
©2019, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • email@example.com