Aaron and Brian talk with Michael Garski (Director of Software Engineering @FenderDigital) about building serverless applications for their Fender Play digital learning platform. He explains how the Lambdas are built, version controlled and tested, as well as provides into the broader architecture and how their Dev and Ops teams are integrated.
Fender Website Fender Digital Fender Play Combining DynamoDB and Amazon Elasticsearch with Lambda [Podcast] Serverless Performance, Monitoring and Best Practices from Fender [PODCAST] @PodCTL - Containers | Kubernetes | OpenShift - RSS Feed, iTunes, Google Play, Stitcher, TuneIn and all your favorite podcast players [A CLOUD GURU] Get The Cloudcast Alexa Skill [A CLOUD GURU] A Cloud Guru Membership - Start your free trial. Unlimited access to the best cloud training and new series to keep you up-to-date on all things AWS. [A CLOUD GURU] FREE access to AWS Certification Exam Prep Guide - At A Cloud Guru, the #1 question received from students is "I want to pass the AWS cert exam, so where do I start?" This course is your answer. [FREE] eBook from O'Reilly
Topic 1 - We appreciate you reaching out to tell us about your experience. So let’s talk about your background prior to Fender and some of the things you focus on at Fender. Topic 1a - Are you a guitar player? Do you have a favorite guitar riff? Topic 2 - We’re going to talk about how you use serverless (AWS Lambda) for Fender Play, but before we do that, I want you to walk us through that the guitar player experiences in the Play framework. Topic 3 - Let’s talk about the challenges in delivering this framework that lead you to consider using Lambda (and other AWS services). Topic 4 - Let’s dive into the architecture that you’ve built. What have been easier to evolve and what challenges have you run into? Topic 5 - Fender Play starts with a free trial and then can evolve to a paid service. How much did your engineering team connect those subscription requirements with your choice of using serverless technologies? Topic 6 - What are some lessons or best-practices that you’d recommend to someone new to serverless (either in development or ops). Feedback?
Email: show at thecloudcast dot net Twitter: @thecloudcastnet and @ServerlessCast