Big Story

API architectures have traditionally assumed a relatively simple deployment model. A company would select one gateway platform, deploy it as the central entry point for APIs, and manage traffic, authentication, and rate limiting through that single layer. As organizations expanded into multi-cloud environments and distributed product teams, this model became increasingly difficult to maintain.

Large enterprises now operate multiple API gateways at the same time. Different business units may adopt different gateway technologies. Some gateways run in public clouds, others in on-premise environments, and additional gateways may sit at the edge or within regional infrastructure. Over time, the architecture evolves into a patchwork of gateway deployments rather than a single centralized system.

This fragmentation introduces new operational challenges. Security policies, authentication rules, and rate-limiting logic must remain consistent across gateways even when the underlying technologies differ. Without coordination, teams risk creating inconsistent access controls or fragmented developer experiences.

Gateway federation has emerged as a strategy for managing this complexity. Instead of enforcing a single gateway product across the entire organization, federation focuses on coordinating policies and governance across multiple gateways. Each gateway continues to operate within its environment, but shared policies and visibility tools provide a unified operational view.

In practice, this approach separates gateway infrastructure from governance. The infrastructure layer may consist of several gateway platforms, while the governance layer ensures that security policies, traffic management rules, and developer access standards remain consistent across them.

This architecture is becoming relevant as API ecosystems grow. Modern organizations often expose hundreds or thousands of APIs across microservices, partner integrations, and internal systems. A federated gateway model allows teams to scale infrastructure without sacrificing control over security, monitoring, and developer access.

Ultimately, gateway federation reflects a broader shift in API management strategy. Rather than treating the gateway as a single centralized appliance, organizations are beginning to view it as part of a distributed system that requires coordinated governance across multiple platforms and environments.

API Feed

Community Spotlight

Mark Boyd is the founder of Platformable, a research organization that studies how API ecosystems evolve across industries such as financial services, digital platforms, and public-sector infrastructure. His work focuses on the operational and economic dynamics of APIs, including how developer ecosystems grow, how API governance affects platform adoption, and how organizations translate API strategy into measurable business outcomes.

Boydʼs research frequently examines the maturity of API ecosystems. Through studies of open banking programs, platform marketplaces, and fintech ecosystems, he has explored how factors such as documentation quality, developer onboarding, governance structures, and ecosystem incentives influence whether an API program attracts meaningful third-party participation. This perspective places API programs within the broader context of platform strategy.

His writing has appeared regularly in developer and platform publications such as Nordic APIs and ProgrammableWeb, where he has written extensively about open banking, platform ecosystems, and API maturity models. Boyd has also presented and moderated discussions at conferences, contributing practitioner-oriented perspectives on API adoption and ecosystem development.

A distinctive aspect of Boydʼs work is his engagement with public-sector API programs and financial inclusion initiatives. Through research collaborations with organizations such as the Consultative Group to Assist the Poor, he has examined how open banking APIs and digital platform infrastructure influence access to financial services in emerging markets. These studies explore how regulatory frameworks, platform governance, and API design decisions shape the ability of fintech developers to build services on top of banking infrastructure.

Across these projects, Boydʼs central argument is that API quality and governance matter beyond the engineering layer. Poorly designed APIs can weaken developer ecosystems, limit competition, and reduce the social benefits of digital platforms. Conversely, well-governed API ecosystems can expand participation, enable innovation by third-party developers, and improve access to digital services across markets.

More recently, Boyd has been involved in discussions around data governance and open data policy through collaborations with institutions such as the Open Data Institute. This work connects API design with broader questions about how governments and institutions structure access to data, a topic that is becoming increasingly important as AI systems depend on reliable digital infrastructure and interoperable data services.

Resources & Events

apidays Singapore brings together API builders, architects, and platform leaders in one of Asiaʼs biggest fintech and digital transformation hubs, with a strong focus on how APIs are evolving for the AI and agentic era. The program blends practical case studies and technical sessions across API management, security, governance, and automation. Details →

apidays New York is positioned as a high-density gathering for teams operating APIs at scale, with sessions spanning monetization, security, AI-driven automation, and platform governance. Itʼs built for senior practitioners and decision-makers, bringing together 1,500+ participants from 1,000+ companies, making it a strong anchor event for anyone tracking where enterprise API strategy is heading next. Details →

You can find a list of all Apidays events here

Apply to speak at Apidays Singapore, NY, London, Paris, and more here 

KubeCon + CloudNativeCon Europe is the Cloud Native Computing Foundation's flagship annual conference, bringing together over 12,000 developers, platform engineers, and technology leaders from across the open source and cloud native ecosystem. The four-day program spans 10+ tracks covering Kubernetes operations, platform engineering, AI integration, observability, security, and supply chain practices. For API and platform teams, the platform engineering and security tracks are particularly relevant as cloud native API infrastructure continues to evolve to support agentic workloads and multi-cluster environments. Details →

📊 Report Spotlight: Global API Management Market Outlook (Fortune Business Insights)

Global demand for API management platforms is expanding quickly as companies rely on APIs to connect cloud services, microservices, and AI applications. The market for API management tools was valued at $6.89 billion in 2025 and is projected to grow to $8.77 billion in 2026, eventually reaching more than $37 billion by 2034. Read →

Insight of the Week

Some developers are questioning whether the Model Context Protocol (MCP) is the right abstraction layer for building AI workflows. Criticism has focused on the protocolʼs operational complexity, including the amount of context it consumes, the need to toggle integrations on and off, and the friction around authentication when connecting tools. These discussions suggest that while MCP offers a standardized interface for AI tool integration, many teams are still evaluating whether the additional abstraction is worth the trade-offs compared with simpler API-driven architectures.

For the Commute

In this talk, integration architect Charles Huyghe explores why enterprises find it difficult to transition from traditional integration models to API-first and event-driven architectures. The friction, he argues, is about legacy practices, skill gaps, and fragmented governance. He proposes a pragmatic path forward of improving architectural visibility, closing capability gaps, and evolving from centralized enablement to decentralized ownership.

Stay tuned for bold ideas, fresh perspectives, and the next wave of API innovation

-The Apidays Team

Visit the Website