November 2023 Summaries

GraphQL has matured into a robust tool, well-used in production, and is no longer the novel technology it once was. The hype surrounding GraphQL has died down, but it's still a stable and reliable choice for solving real-world problems. Its strengths lie in API composition, federating data dependencies, and bridging organizational divides between frontend and backend teams. While it may not be an all-encompassing substitute for REST APIs, GraphQL carves out unique niches and can be used to solve specific problems. The adoption of GraphQL is growing, particularly in enterprise environments where federation can help bring together disparate APIs, microservices, and data sources into a unified interface. WunderGraph is a tool that makes it easy for enterprises to adopt GraphQL without licensing hurdles, offering features like persisted queries, blazingly fast caching strategies, and distributed autonomy. Its successor, WunderGraph Cosmo, is an open-source platform for GraphQL Federation, built on open standards and containing everything needed to build, manage, and collaborate on federated graphs at scale. Ultimately, GraphQL's transition to a stable workhorse is a testament to its maturity, and it's poised to become even more important as diverse API styles become increasingly prevalent.

The `astjson` package is a Go library that allows for efficient transformation and merging of JSON objects by parsing them into an Abstract Syntax Tree (AST) exactly once, then modifying the AST as needed without touching the actual JSON content. This approach eliminates the need to parse and merge JSON objects repeatedly, reducing CPU time and memory usage. The package simplifies non-null error bubbling in GraphQL responses by walking through both the GraphQL AST and the JSON AST in parallel and "deleting" fields that are not present in the GraphQL AST. Benchmarks show significant improvements in throughput and latency for a GraphQL API Gateway built using this approach, making it an attractive solution for building high-performance APIs.

API Composition` is a paradigm that enables the creation of added value by integrating certain services, functionality, and data through their respective APIs to form a new service or product. This approach allows businesses to build personalized service stacks for their companies and add seamless user interfaces on top. Understanding `APIs`, `API Composition`, and the `MACH` (Microservices, API-first, Cloud-native, Headless) paradigm is crucial for executives to make informed decisions, speed up time-to-market, gain stack flexibility, and create business opportunities. However, API Composition also comes with risks and challenges, such as dependency risks, security concerns, and performance issues, which need to be carefully addressed. As the technological landscape continues to evolve, API Composition will play a vital role in shaping the future of digital transformation, IoT, AI, and ML.

Cosmo is an API integration SDK that meets compliance requirements and saves onboarding time for businesses. By being open-source, allowing customization, having a community-driven review process, and running fully self-hosted, Cosmo simplifies the due diligence process for companies looking to adopt new software or vendors. This results in faster time-to-market, reduced egress costs, and improved compliance with regulatory requirements such as ISMS / ISO 27001. By avoiding cloud dependencies and allowing businesses to run critical software in their own infrastructure, Cosmo provides a unique solution that balances business needs with security and privacy concerns.

The text discusses the shift from monolithic to federated architectures in software development, with a focus on GraphQL. Federated architectures offer modularity, scalability, and maintainability, addressing the limitations of traditional monolithic systems. By dividing the schema into smaller subgraphs, developers can work independently, speed up development, and simplify maintenance. This approach also optimizes performance by minimizing data over-fetching and enables seamless scalability. The text highlights notable adoptions of Federated GraphQL in large-scale applications and notes its suitability for high-traffic and complex systems. While migration to Federated GraphQL requires planning and expert guidance, its popularity continues to grow, indicating a positive outlook for its future adoption.

There are multiple reasons why analyzing your GraphQL Schema's usage is beneficial, including optimizing the API to better suit clients' needs, improving documentation, and safely removing or deprecating unused fields. Implementing schema usage analytics involves dividing the process into three parts: response type field usage, field arguments usage, and input type field usage analysis. By analyzing these aspects, you can gain insights into how your GraphQL Schema is being used and use this information to implement breaking change detection, ensuring that changes do not break existing clients.

There are multiple reasons why analyzing your GraphQL Schema's usage is important, including optimizing APIs to better suit clients' needs, documenting the most used fields, deprecating unused fields, and safely removing deprecated fields without breaking them. To analyze schema usage, you can divide the task into three parts: response type field usage, field arguments usage, and input type field usage. By analyzing these parts, you can gain insights into how your GraphQL Schema is being used and use this information to implement breaking change detection, which involves comparing changes to the Schema or one of your Subgraphs to the last known good version and finding potential breaking changes that would affect clients using specific fields, arguments, or input types.