Скачать с ютуб API Terminology Explained: Gateways, Portals, Catalogs, Marketplaces в хорошем качестве

API Terminology Explained: Gateways, Portals, Catalogs, Marketplaces

API management revolves around managing individual APIs as well as API landscapes, i.e. the set of APIs that are provided and used by organizations. APIs have been around for quite a while, and for this reason, there are some components that have become commoditized building blocks for API management. In this video, Jaime Ryan of Axway explains a few concepts in this space, which are gateways, portals, catalogs, and marketplaces. Gateways are probably the most commoditized component in the API space, they are used to secure and manage individual APIs. Portals often are used to expose the set of APIs that is managed through a gateway, meaning that they can be coupled relatively tightly to the way API management is done at a technical level. Catalogs are a layer that is independent of technical management. Because catalogs are not tightly coupled to a gateway, catalogs are a good way to consolidate APIs across heterogeneous environments, for example when multiple API gateways are part of an organization's infrastructure. Marketplaces historically started as a more "outside-in" way of managing APIs, allowing everybody to contribute APIs (regardless of their technical management) to the marketplace. More recently, this concepts is gaining momentum as an enterprise-level concept, meaning that the more "inside-out" oriented nature of portals now can be replaced or combined with the more "outside-in" oriented nature of marketplaces. 00:00 Introduction 01:18 API Gateways 02:41 API Portals 04:58 API Catalogs 07:40 API Marketplace 11:20 Difference Portal/Marketplace