The engineering career framework at WunderGraph fosters growth, progression, and scaling teams with transparency, fairness, and strong culture.| WunderGraph
Learn how to use Go’s sync.WaitGroup correctly with real-world examples, common mistakes, and performance tips. Avoid deadlocks, leaks, and master goroutine management.| WunderGraph
A deep dive into Go's sync.Pool, its benefits, pitfalls, and when to use it (or not)| WunderGraph
How the team at SoundCloud saved 86% on infrastructure costs for their GraphQL Federation deployment by moving to WunderGraph Cosmo.| WunderGraph
Discover how GraphQL Federation supports the Open/Closed Principle (OCP) in API development, enabling scalable and extensible microservices without modifying existing code. Learn why REST APIs struggle with OCP, see real-world examples from game development, and explore how SuperGraph and Apollo Federation make API evolution seamless. A must-read for developers looking to future-proof their architecture!| WunderGraph
Big events like the Super Bowl or Black Friday can put a lot of stress on your federated GraphQL API. This post dives into the engineering behind scaling a federated GraphQL API for the big game.| WunderGraph
A few weeks ago, one of our customers came to us with an interesting problem: they wanted explicit and granular control over the descriptions that were propagated to their federated graph. As I'm sure you're aware, most constituents of a GraphQL schema may define a description; and an instance of a constituent (coordinates) could appear in multiple subgraphs—each with its own bespoke description. However, only one description can be propagated to the federated graph.| WunderGraph
Why WunderGraph builds its cloud solution in public and choses transparency over secrecy.| WunderGraph