Building a Better Web
June 19–20, 2017: Training
June 20–22, 2017: Tutorials & Conference
San Jose, CA

Schedule: Microservices sessions

1:30pm–5:00pm Tuesday, June 20, 2017
Fullstack Development
Location: 210 CG
Kevin Old (LifeWay)
Average rating: **...
(2.62, 8 ratings)
Kevin Old explores the principles of serverless architecture as he walks you through building and deploying a service on AWS Lambda that retrieves data from DynamoDB via GraphQL. Along the way, you'll learn how to use the Serverless Framework to ease the burdens of managing the lifecycle and deploying services in a serverless architecture. Read more.
3:35pm–4:15pm Wednesday, June 21, 2017
Fullstack Development
Location: 210 AE
Shane Russell (United States Digital Service)
Average rating: ***..
(3.62, 8 ratings)
The US Digital Service is building a suite of tools to replace a large legacy application at the Department of Veteran Affairs. Knowing the complexity of the end state and enamored with microservices, the team was much too aggressive in breaking up the product. Shane Russell reflects on this experience, sharing advice and lessons learned on how and when to break up your web app. Read more.
4:25pm–5:05pm Wednesday, June 21, 2017
Web Services and APIs
Location: 210 BF
Average rating: ****.
(4.00, 6 ratings)
In the new world of JavaScript UIs, REST APIs, and microservices, applications that run in the highly insecure browser environment must handle tokens and other secrets to have access to backend services. Drawing on his experience at Rackspace, Miguel Grinberg discusses the risks and shares best practices to avoid them. Read more.
4:25pm–5:05pm Thursday, June 22, 2017
Web Services and APIs
Location: 212 A/B
Ruthie Nachmany (Warby Parker)
Average rating: ***..
(3.50, 2 ratings)
Warby Parker recently built an electronic health record system for its optometrists to use to conduct and store their eye exams. The company used this project as an opportunity to explore building a serverless web application on AWS. Ruthie Nachmany shares details of the system's implementation, challenges faced, and lessons learned along the way. Read more.