Programmatic Microservices by Randy Shoup, VP Engineering @ WeWork

Name: Programmatic Microservices by Randy Shoup, VP Engineering @ WeWork
Uploaded: 2019-04-01

Posted Apr 01, 2019 | Views 258

# Technology

# AI

# Cross-Functional Teams

# Data Science

# DevOps

# Engineering Process

SPEAKER

Randy Shoup

VP Engineering and Chief Architect @ eBay

Randy Shoup (https://www.linkedin.com/in/randyshoup/) is a 25-year veteran of Silicon Valley, and has worked as a senior technology leader and executive at companies ranging from small startups, to mid-sized places, to eBay and Google. Randy is currently VP Engineering at Stitch Fix (https://www.stitchfix.com/) in San Francisco.

Earlier, Randy was Chief Engineer at eBay for 6 1/2 years, where he was responsible for multiple generations of eBay's realtime search infrastructure. He was CTO and Co-founder of a startup, and learned just how difficult and different it is to build a company from scratch. He was Director of Engineering at Google for Google App Engine, the world's largest platform-as-a-service. He also spent a year and a half applying eBay and Google lessons consulting with startups and large enterprises on how to improve their organizations and technology.

He is particularly passionate about the nexus of culture, technology, and organization.

+ Read More

He is particularly passionate about the nexus of culture, technology, and organization.

+ Read More

SUMMARY

One of the most powerful trends in software today is building large systems out of composable microservices. Many large-scale web companies have migrated over time to this architecture – and for good reason. But, as with any powerful technique, microservices come with their own brand of tradeoffs, and it is important to be aware of them before deciding whether they are appropriate in any particular case. They are not for every scale of problem, for every stage of company, or for every team.

This session takes a pragmatic approach to microservices and compares them to the alternatives at different stages of company evolution. Using examples from Google, eBay, and Stitch Fix, as well as from smaller organizations, it makes practical suggestions about whether, when, and how an organization should consider adopting a microservices architecture. Assuming microservices are the appropriate choice, it outlines an experience-based, incremental approach to making a successful re-architecture to microservices.

+ Read More