in the API industry
The goal of APIIDA is to increase vendor-independent competition, which has been proven to lead to better products and lower costs. API management thus becomes a discipline in its own right and can drive disruptive change in the industry.
from API 1.0 to API 3.0
Our approach to API management evolved from the service-oriented architectures of the 1990s. Broadcom’s Layer7 API Gateway, for example, is rooted in the idea of acting as a proxy between consumers and upstream services, rather than integrating relatively complex specifications into each individual web service.
Later, in addition to traffic going in and out of the enterprise, traffic within the enterprise also gained relevance. With a wave of new thinking and architectures came API management platforms that merged traditional 1.0 gateways with new services, giving rise to API 2.0 platforms. The provision of free open source packages significantly lowered the price of professional API management. The final evolution of API 3.0 platforms came from the rise of the Internet of Things and new design principles that drove so-called streaming APIs, or asynchronous, event-driven APIs. Changing protocols brought additional change as they were not supported by all API platforms. The trend towards specialization led to a very heterogeneous landscape.
New way of
thinking about API management
What clearly sets APIIDA’s approach apart is not only its support of individual API management, but more importantly its perspective on operations. We not only look at collaboration and design, but share the company’s perspective and focus.