Frances Johnson, Google Australia
Client isolation is an important consideration for the reliability of Google Maps. We want to avoid becoming overloaded where possible and degrade gracefully otherwise. Following some user-visible outages in the area, Geo SRE began working on implementing client isolation.
But these things are never easy. There are multiple points in the stack where you can drop traffic so where should you do it and what are the tradeoffs? Are all requests created equal? What if your system changes partway through? Why doesn't exempting important traffic make sense? What other unexpected benefits does client isolation give you? All this and more!
Attendees will learn about what goals you can set for traffic management, identifying characteristics of your traffic and system architecture to leverage, and the strategies which can be used to design the solution.
Frances Johnson, Google Australia
I'm an SRE at Google in Sydney working on Spanner, formerly Geo (Maps).
Open Access Media
USENIX is committed to Open Access to the research presented at our events. Papers and proceedings are freely available to everyone once the event begins. Any video, audio, and/or slides that are posted after the event are also free and open to everyone. Support USENIX and our commitment to Open Access.
author = {Frances Johnson},
title = {How to Serve and Protect (with Client Isolation)},
year = {2018},
publisher = {USENIX Association},
month = jun
}