API Scope and Design: Internal/External? Private/Partner/Public? скачать в хорошем качестве

API Scope and Design: Internal/External? Private/Partner/Public?

In this interview with Kin Lane (the API Evangelist), we talk about API scope and design and real and imagined ideas of control that come along with these notions. "Internal/External" is a difference that often is driven by technical considerations: is the API exposed internally only, or can it be consumed externally because it is exposed outside of the firewall? In an increasingly fluid world where platform models and strategic partnerships abound, this technical differentiation may not be the best way to think about your API products anymore. "Private/Partner/Public" takes a more consumer and design-oriented approach and looks at who an API is for. For example, a private API that is powering apps (we're using the example of an GraphQL API for mobile and web apps) may still be "external" because it needs to be exposed to wherever those apps run. We come away with the conclusion that a more holistic and product-oriented view of APIs can make a difference. Moving the focus from technical aspects to consumers and a clear value proposition helps to design and build better products. It also helps to better identify and quantify the value that APIs are producing so that "API management" can also level up from purely technical aspects to a more value-focused perspective.