Скачать или смотреть Designing Private, Partner, and Public APIs: What's the Difference?

APIs are meant to be reusable, and thus should be designed so that potential API consumers find the API usable and useful. The API scope is one important design constraint that can help to inform API design, and thus to create a better API.

Private APIs are consumed within an organization and thus there is an existing and relatively tight coupling between API consumers and API producers. Partner APIs are consumed in the context of some partner program, and even though consumers are outside of the organization, there is an established relationship. Public APIs are consumed without such relationship, and thus there only is a very loose coupling between consumers and producers.

In this video, we look at four design constraints that are affected by the difference between Private, Partner, and Public APIs. We look at how domain knowledge, consumer relationships, security issues, and API landscape questions are affected, and how it's possible to design better APIs when taking these constraints into consideration.


00:00 Introduction
01:01 System APIs
01:35 Definition: Private/Partner/Public APIs
02:41 Four API Design Constraints
04:13 Domain Knowledge
05:31 Relationship with Consumers
07:08 Security & Threat Model
09:03 API Landscape Context
10:57 Wrap-Up