After six years of building GraphQL tools and writing about it, I'd like to revisit some of my old opinions and see how they hold up with my knowledge and experience today.

Wundergraph is a blog or publication focused on GraphQL, a query language and runtime for APIs. Through tutorials, guides, and case studies, Wundergraph explores various aspects of GraphQL development, including schema design, query optimization, and integration with frontend frameworks. Developers can learn how to leverage GraphQL to build efficient and flexible APIs that meet the needs of modern web and mobile applications.

WunderGraph

The author revisits and reassesses previous opinions on GraphQL based on current knowledge and experiences. Key insights include the importance of building on top of existing tools and patterns rather than introducing new ones, the organizational benefits of GraphQL Federation, and the evolution of best practices such as using persisted queries and APQ. The author also reflects on the practical challenges and benefits of GraphQL for large-scale enterprise applications, particularly in terms of caching, API design, and Subscriptions implementation.

I was wrong about GraphQL

GraphQL is not meant to be exposed over the Internet

The case against normalized Caching in GraphQL

Generated GraphQL APIs: Tight Coupling as a Service

GraphQL Namespacing: Conflict-free merging of any number of APIs

API Design Best Practices for long-running Operations: GraphQL vs REST

GraphQL Subscriptions: Why we use SSE/Fetch over Websockets

GraphQL's @defer and @stream Directives are overkill

When to use GraphQL vs Federation vs tRPC vs REST vs gRPC vs AsyncAPI vs WebHooks—A 2024 Comparison

Comparisons of GraphQL should mention Relay

<p>I highly respect the revisit opinions from the past, especially when you make a living from it.
In these days when everyone is thinking he’s right, this is rare.</p>
