February 2025 Summaries

GraphQL Federation Architecture: An Open/Closed Principle and Project-Based SuperGraphs approach is being discussed, where a modular, reusable API architecture is leveraged to support development teams working on multiple similar projects. This approach utilizes the Open/Closed Principle, which states that software entities should be open for extension but closed for modification. In the context of API development, GraphQL Federation supports this principle and offers benefits such as independent extensibility and minimal risk when it comes to breaking changes. Traditional REST APIs struggle with OCP, requiring constant modifications and versioning. By using GraphQL Federation, developers can build modular, scalable API architectures that evolve without modifying existing services, making it ideal for project-based development like in game development where multiple teams work on different projects.

The Supergraph Kickoff post discusses scaling a federated GraphQL Router to handle high traffic spikes, such as during events like the Super Bowl. The article highlights the importance of identifying bottlenecks in a federated GraphQL API and provides an overview of how Cosmo Router achieves this by implementing a heuristics-based cache warm-up strategy. This strategy eliminates cold starts and ensures that the Router can serve traffic efficiently without downtime. The post also touches on alternative approaches to warming up caches, such as using persisted queries or trusted documents, but notes their limitations. Overall, the article provides valuable insights into optimizing the performance of a federated GraphQL Router and showcases Cosmo Router's capabilities in handling high-traffic scenarios.

The `@configureDescription` directive for GraphQL Federation aims to provide schema designers with fine-grained control over how descriptions are propagated, overridden, or hidden from the federated graph. This directive addresses issues such as inconsistent, redundant, or misleading descriptions that can lead to confusion and errors for API consumers. It offers four main functions: propagating a description, overriding a description, preventing the propagation of a description, and propagating a description through an extension type. The constraints for using this directive are relatively simple, ensuring explicit and collaborative use. By adopting this directive, teams can streamline their API documentation, enhance the developer experience, and improve the overall consistency of their federated schemas.

GraphQL schema usage data is crucial for understanding how a GraphQL API is being utilized, especially in federated architectures where multiple services contribute to the overall schema. To address the challenges of managing GraphQL schema usage at scale, we need to collect and process this data efficiently. We've implemented a robust system that handles high data volume, throughput, and latency by batching, queuing, and regional deployment. The system uses Kafka as a buffer to absorb client-side traffic spikes while being able to ingest data into ClickHouse at a constant rate in large batches. This setup allows us to accept data at a much higher rate than ClickHouse can ingest while consuming it at a rate that ClickHouse can handle. We've also implemented real-time ETL streaming pipeline using ClickPipes, which eliminates the need for implementing and maintaining a custom ETL pipeline from scratch. The system is highly available and can handle billions of requests per day, with features like horizontal scaling, high availability, regional deployment, and global load balancing. Observability and monitoring are also crucial, with instrumented metrics and alerting rules to notify us of any anomalies or issues.

On The Beach`, a leading UK travel company, leveraged WunderGraph Cosmo to modernize its GraphQL architecture and overcome scalability challenges. Initially, they built a custom GraphQL Federation but struggled with maintenance and complexity. Adopting Cosmo enabled streamlined schema management, reduced operational complexity, and improved developer experience with advanced request tracing. Event-Driven Federated Subscriptions revolutionized real-time data handling, while Advanced Request Tracing boosted performance and profitability. The Cosmo Schema Registry centralized schema management, simplifying API development and unlocking efficiency. By offloading outdated functionality and distributing responsibilities to domain-specific teams, On The Beach improved scalability and reduced maintenance burdens. Their collaboration with WunderGraph ensured a smooth transition, providing hands-on guidance and exceptional support. Looking ahead, On The Beach plans to deepen their use of Cosmo's features to continue enhancing real-time data capabilities and exploring ways to extend the hybrid architecture for scalability and cost efficiency.