Show simple item record

dc.contributor.authorAhmad, Mak
dc.contributor.authorGeewax, J. J.
dc.contributor.authorMacvean, Andrew
dc.contributor.authorKarger, David
dc.contributor.authorMa, Kwan-Liu
dc.date.accessioned2024-06-05T16:16:02Z
dc.date.available2024-06-05T16:16:02Z
dc.date.issued2024-04-14
dc.identifier.isbn979-8-4007-0501-4
dc.identifier.urihttps://hdl.handle.net/1721.1/155197
dc.descriptionICSE-SEIP '24: Proceedings of the 46th International Conference on Software Engineering: Software Engineering in Practice April 14–20, 2024, Lisbon, Portugalen_US
dc.description.abstractAPI Governance, the process of applying standardized sets of policies and guardrails to the design and development of APIs, has only grown in importance and prominence given the continued growth in APIs being produced. In this paper, we present an Action Research style approach to investigate and understand the utility of a multi-faceted API Governance process being adopted inside Google. We first reflect on past research around API Governance, and then introduce three new components, 1. API Improvement Proposals (AIPs) the documented source of truth for API design rules, 2. API Linter, an automated analysis tool which checks for adherence to / violations of AIPs, and 3. API Readability, a program to educate and certify API design experts. These three components are designed to build upon pre-existing processes to scale and improve API design. Through a mixed-methods research strategy, containing both a survey and a series of interviews, we evaluate the utility of these approaches in supporting API Producers. Our research shows that API Producers have positive sentiment towards API Governance, validating the general direction of the program. Specifically, our study participants highlighted the positive impact of API Governance on the quality of the APIs they produced, via consistency in both the outcome and approach. This paper also discusses future research opportunities to enhance API Governance, specifically with regards to newer API Producers, who reported worse sentiment towards the program than their more experienced peers.en_US
dc.publisherACMen_US
dc.relation.isversionof10.1145/3639477.3639713en_US
dc.rightsCreative Commons Attributionen_US
dc.rights.urihttps://creativecommons.org/licenses/by/4.0/en_US
dc.sourceAssociation for Computing Machineryen_US
dc.titleAPI Governance at Scaleen_US
dc.typeArticleen_US
dc.identifier.citationAhmad, Mak, Geewax, J. J., Macvean, Andrew, Karger, David and Ma, Kwan-Liu. 2024. "API Governance at Scale."
dc.contributor.departmentMassachusetts Institute of Technology. Computer Science and Artificial Intelligence Laboratory
dc.identifier.mitlicensePUBLISHER_CC
dc.eprint.versionFinal published versionen_US
dc.type.urihttp://purl.org/eprint/type/ConferencePaperen_US
eprint.statushttp://purl.org/eprint/status/NonPeerRevieweden_US
dc.date.updated2024-06-01T07:56:29Z
dc.language.rfc3066en
dc.rights.holderThe author(s)
dspace.date.submission2024-06-01T07:56:29Z
mit.licensePUBLISHER_CC
mit.metadata.statusAuthority Work and Publication Information Neededen_US


Files in this item

Thumbnail
Thumbnail

This item appears in the following Collection(s)

Show simple item record