May 2025 Summaries

The declarative approach to API orchestration, popularized by Apollo Connectors, has several fundamental technical problems. These include GraphQL Directives not being designed for infrastructure as code, the verbosity of the `@connect` directive making it hard to understand and maintain complex scenarios, the leaking of implementation details into the GraphQL SDL, and the N+1 problem caused by the declarative nature of the approach. Additionally, testing and debugging connectors is challenging due to their reliance on human-centric workflows and the lack of standard testing frameworks. In contrast, gRPC Plugins, which utilize Generative AI (LLMs) to generate code for API orchestration, offer a more scalable, efficient, and maintainable solution with features such as easy testability, high performance, and support for multiple languages.

When I started at WunderGraph, I was assigned to build a small UI feature inside Cosmo Studio for managing GraphQL federation. The task involved designing and implementing a shareable Playground session link with compression, state restoration, and UI flow considerations. After refining the code and addressing feedback, it shipped in production with actual users, including companies like SoundCloud. Through this experience, I learned about ownership, communication, prioritization, and the importance of treating tasks like real features. It also showed me that WunderGraph values trust, autonomy, and thoughtful engineering, and I was able to dive into a complex codebase and contribute to something real from day one.

Cosmo OSS is a powerful way to start with GraphQL Federation, providing speed, flexibility, and open-source capabilities. As teams grow and systems become more complex, managing everything in-house can become harder due to operational overhead, limited visibility, and compliance requirements. Cosmo Enterprise builds on the same core and adds governance, observability, and support needed to scale with confidence without starting over. It's ideal for early adoption, internal evaluations, or rolling out Federation in lower environments before considering the full platform. While open-source OSS is not free and requires collaboration rather than consumption, it can be an excellent choice for small projects or initial evaluations. However, as teams grow and requirements become more complex, migrating to Cosmo Enterprise may be necessary due to increased operational burden, limited visibility, compliance pressure, and performance issues. The platform provides governance, observability, support, and scalability features to help teams move forward safely with incremental, non-disruptive migrations.

Go's `sync.WaitGroup` is a powerful primitive for synchronization in concurrent code, but it can be tricky to use effectively. It allows you to wait for multiple goroutines to finish and provides a way to ensure that the main goroutine doesn't exit before all workers are done. However, if not used correctly, it can lead to bugs like deadlocks or improper cancellation. The key is understanding the lifecycle of a goroutine and using `context.Context` to manage cancellation and deadlines. In some cases, an alternative approach using `errgroup.Group` provides richer error handling and cancellation logic, making it more suitable for complex concurrent patterns. Always think about the entire lifecycle of your goroutines and use tools like `goleak` to test for potential leaks.