July 2025 Summaries

WunderGraph, known for its Cosmo platform managing federated GraphQL APIs, is a globally distributed team that has recently closed a Series A funding round, enhancing its momentum in developing new developer tools. The company emphasizes its collaborative culture through a Manifesto outlining 17 core beliefs, which are used for hiring, onboarding, and maintaining alignment. This Manifesto, not just a symbolic gesture, serves as a practical guide for employees, reflecting the company's commitment to innovation and rapid problem-solving. WunderGraph operates with a flat organizational structure, encouraging ownership, direct communication, and a customer-centric approach while fostering a remote-first, flexible work environment. The Manifesto continues to evolve to support the company's growth, with plans for future retreats and a Values framework to further embed its culture. The company is expanding its U.S. market presence and launching WunderGraph Hub, a collaborative platform for API development, reinforcing its mission of building the future of API collaboration.

Kevin Swiber, an independent expert with extensive experience in the API ecosystem, discusses various topics on The Good Thing podcast, including the Model Context Protocol (MCP), AI's role in developer tools, and the importance of "boring" infrastructure. Swiber emphasizes that while AI and MCP are gaining attention, many companies are just beginning to explore AI tools, and infrastructure stability is valued over innovation. He highlights the challenges of API governance in distributed teams and argues that while AI might change the landscape, it won't eliminate the need for APIs. Swiber also reflects on the resurgence of hypermedia patterns through MCP and the parallels between LLM interfaces and the early web, noting the impact on web experiences and ad revenue. Finally, he underscores the cyclical nature of technological trends and the enduring relevance of tools like GraphQL within broader frameworks.

Luxury Presence, a company powering over 50,000 real estate websites, transitioned from a backend-for-frontend (BFF) architecture to using WunderGraph Cosmo to improve development efficiency and reduce duplication. This architectural shift was driven by the need to unify fragmented systems and meet increasing customer expectations, enabling up to 40 daily deployments and faster feature rollouts with fewer engineers. The adoption of Cosmo allowed for a progressive migration, replacing REST endpoints with GraphQL interfaces, and fostering a consistent development environment with shared TypeScript types. This change facilitated a more streamlined release process, improved developer velocity, and reduced complexity for new engineers by eliminating the BFF layer. Additionally, the visual schema tools in Cosmo aided teams in understanding system connections, while the platform's collaborative features and customer support contributed to a culture of shared development focus and reduced operational friction.

Apollo Federation, introduced in 2019, has evolved to address the complexities of scaling GraphQL schemas by enabling the division of a GraphQL schema into subgraphs, thus facilitating a microservice architecture. Despite its advantages, such as allowing client engineers to interact with a single unified schema and supporting declarative relationships via @key, the system has significant design and scaling issues, notably the leakage of query planning details into subgraphs, performance bottlenecks, and the complexity of implementing @requires. These challenges have prompted discussions on new approaches, including a Composite Schema specification and the use of Proto+gRPC for subgraphs, which aim to simplify subgraph implementations and enhance performance. The article suggests that while GraphQL Federation is powerful, the community is still working on refining the model to optimize its scalability for large enterprises.

In a detailed exploration of GraphQL Federation through the analogy of Cosmo's Food Park, the text explains how Cosmo, the coordinator, manages schema composition, request routing, and error handling to ensure a seamless customer experience. Each food truck operates independently, but Cosmo compiles their individual menus into a unified, park-wide menu, resolving conflicts and ensuring consistency through schema composition. When orders are placed, Cosmo efficiently routes each part to the correct kitchen and gracefully handles any errors, preventing disruptions in service. Real-time updates are managed through Event-Driven Federated Subscriptions, allowing Cosmo to keep customers informed without constant polling. The analogy highlights WunderGraph Hub's capabilities to simplify API management by handling complexities like composition, routing, and subscriptions, enabling teams to focus on broader operational goals without building federation logic from scratch.

WunderGraph introduced a new role-based access control system called "Groups" in its Cosmo platform to address inconsistencies in permissions and provide centralized management across federated GraphQL APIs. This system allows easier management of permissions by grouping users and API keys under unified rules, streamlining access to namespaces, graphs, and subgraphs while ensuring that users see only the resources they have permission to access. The system replaces previous disparate configurations with a more flexible and secure model, enhancing both user experience and security by hiding unauthorized resources from view and enforcing permission checks throughout the platform. The changes were driven by customer feedback and aim to simplify permission management and audits, providing roles like Admin, Viewer, and Publisher for both users and API keys. Existing users and API keys have been automatically migrated to this new system, although it is recommended to transition to Groups for improved clarity and maintainability. The introduction of Cosmo Groups represents a significant enhancement in how WunderGraph manages access control, making it easier for organizations to define access once and apply it consistently across their systems.