The Human Side of Microservices John Billings @jnb42 billings@yelp.com
Introduction
About me • PhD in compiling and verifying routing protocols • Joined Yelp in February 2011 • Initially: • Joined <10 person search team • 70 - 80 engineers • Now 300+ engineers
Yelp’s Mission Connecting people with great local businesses.
Yelp Stats As of Q1 2016 90M 102M 70% 32
LoC in monolith 3 million 1 million 2005 2011 2016
Number of microservices 117 2012 2016
LoC in microservices 891k 2012 2016
Microservice adoption
https://www.flickr.com/photos/24736216@N07/4433492189
“The Diffusion Process” George M. Beal and Joe M. Bohlen, 1957 http://www.soc.iastate.edu/extension/pub/comm/SP18.pdf
Technology adoption curve for a population
The chasm Early adopters Early majority
Innovators
Innovators
The Geocoder Service
Early adopters
The majority
Education
https://en.wikipedia.org/wiki/Fallacies_of_distributed_computing
https://github.com/Yelp/service- principles
● ● Service type (PaaSTA vs legacy SOA) Hardware requirements ● ● Technology type (Python / Java / daemon) Load balancing ● ● Caching Performance and uptime ● ● Downtime scenarios Monitoring ● ● Databases Security ● External services
Summits and unconferences
Talks
Deputy programs
Office hours
Postmortems
Boo! Boring! Standards Tell me Zzzz………….! something interesting!
Interfaces
Perform a real query
Tracing
Metrics
Datastores
Timeouts and retries https://en.wikipedia.org/wiki/Abort,_Retry,_Fail%3F#/media/File:Abort_Retry_Fail.PNG
Ownership
Organizational objectives
Lots of (potentially) conflicting objectives: • Performance • Reliability • Cost • Security • Iteration speed
“What gets measured gets improved” Peter Drucker
Conclusions
Microservices have forced us to build a more robust, decentralized organization
This change has taken a long time
I believe (but cannot prove) that we are shipping code as quickly as ever
Any questions?
Recommend
More recommend
