Six Questions for Kesha Williams of AWS Machine Learning in Motion
Kesha Williams is a full-stack web developer specializing in Java and AWS. She has won numerous awards for her innovative development, as well as her work as a college professor, speaker, tech blogger, and mentor. The founder of Colors of STEM, which cultivates role models to inspire girls of all races to enter the science and tech fields.
Six Questions for Yan Cui, instructor of Production-Ready Serverless
Bio: Yan Cui has worked with AWS for almost a decade, and has contributed his knowledge of production AWS Lamda to the Well-Architected whitepaper published by AWS. Based in London, he travels all over the world giving talks and workshops on serverless. This year he has presented in Copenhagen, Milan, Las Vegas, Portland, Tel Aviv, Krakow, and many more. His blog on The Burning Monk covers his favorite topics, including AWS, serverless, functional programming and chaos engineering.
From Serverless Applications with Node.js by Slobodan Stojanović and Aleksandar Simović
To understand serverless, consider for a moment washing machines. This might sound like a crazy place to start, but owning a server nowadays is similar to owning a washing machine. Everybody needs to clean their clothes, and the most logical solution seems to be buying a washing machine. But most of the time the washing machine is plugged in, it’s doing nothing. At best, it’s used five to fifteen hours per week. Same goes with servers. Most of the time, your average application server is waiting to receive a request, doing nothing.
From Serverless Architectures on AWS by Peter Sbarski
This article takes a close look at the API Gateway. We’ll look at the fundamental activities that go into building an API and discuss features such as staging and versioning, as well as caching, logging, and throttling of requests.
From AWS Lambda in Action by Danilo Poccia
When configuring the Amazon API Gateway to use Lambda functions, you can choose to have no authentication and leave the API publicly available. Using this option together with the HTTP GET method allows your API to be called by a web browser. You need to return the expected content type for HTML (text/html) to implement a public website.