It’s natural in many projects to put the responsibility of responding to API calls, with their highly variable computing needs, on the same infrastructure that serves web pages and assets. A serverless architecture that uses API Gateway to route calls to AWS Lambda for on-demand, pay-by-the-millisecond execution removes load from web servers and scales flawlessly to handle any volume while keeping you from paying for an instant of wasted idle time. Bill Boulden walks you through creating a functioning serverless API that coexists alongside conventionally served web pages using AWS Lambda and API Gateway.
Topics include:
Bill Boulden is the chief technology officer of ClearView Social, where he has migrated a VM-driven infrastructure to an autoscaling application fleet with serverless components. Bill has been developing software since the age of six. Previously, he was an API architect at Delaware North Companies. Running serverless applications in production has given him a unique perspective on architecture and application delivery for modern companies. In his spare time, he’s a pink-haired house music DJ by the name of Spruke, who enjoys EDM and generative ambient music.
Comments on this page are now closed.
For exhibition and sponsorship opportunities, email velocity@oreilly.com
For information on trade opportunities with O'Reilly conferences, email partners@oreilly.com
View a complete list of Velocity contacts
©2018, 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. • confreg@oreilly.com
Comments
@Brian Clarkson, no, it will only be lightly touched on. API Gateway contains many controls for automatically introducing authentication, but they’re beyond the scope of this session.
Will serverless API security be covered in this tutorial?