Justin Coffey, Criteo
Building an SDK or embedded libraries for client teams to integrate into their software seems like a straightforward approach to onboarding a large number of teams onto your infrastructure. Depending on the domain, it can even seem like an obvious and durable decision. Unfortunately, this path is mired with hidden complexity that can have serious productivity consequences for client teams, increasing support related toil for the SRE team significantly and imperiling the viability of both the team and the service they provide.
Justin Coffey, Criteo
Justin Coffey is an engineering director in the SRE department of Criteo where he has led efforts in building out much of Criteo's data processing platform. In past lives he has built ecommerce, emailing and real estate platforms. He got his start in the industry way back in 1996 as a sysadmin working for a small ISP in San Diego, CONNECTnet.
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 = {Justin Coffey},
title = {{SDKs} Are Not Services and What This Means for {SREs}},
year = {2019},
address = {Dublin},
publisher = {USENIX Association},
month = oct
}