As enterprises modernize their IT infrastructure and adopt cloud and mobility initiatives, they find themselves embracing APIs to drive internal application development and integration. However, the one-size-fits-all approach does not work with API portals. Internal development communities are often more sophisticated than open or public communities, said
Compared to open or public APIs, internal APIs have many distinct characteristics that require a different approach to management and security. While an enterprise might have only a few external APIs, it might deploy hundreds of internal services delivered in multiple protocols and transports including REST, SOAP, and POX, over HTTP/S, AMQP, MQ, JMS. To foster re-use, speed, efficiency, and agile application development, enterprises need to be able to publish their internal APIs in a searchable catalog. They need all the capabilities of an external API portal but combined with the kind of security controls and visibility restrictions often required for internal scenarios.
Modeled on open API developer communities but adapted for the enterprise, the API catalog features a feature-rich internal developer portal. Services can be imported directly into the API catalog from existing repositories. From the portal, developers can engage with one another, learn about available APIs, make agreements to use them, and integrate them into the application development lifecycle (ALM.)
Most Popular Stories
- Criminal Investigation Opened Into James Foley's Death
- The Hip New Career? Farming
- McDonald's Names Another U.S. President
- Student Startup Develops Date-rape Detector
- Sahara Casino Rises Anew as SLS Las Vegas
- Chinese Coal Gas Boom Poses Climate Risks
- U.S. Supporters of Islamic State Get Close Scrutiny
- Job Market Shifts Complicate Yellen's Rate Decision
- Dems Losing Fear of Obamacare
- Is Diversity in the Eye of the Beholder?