Tag: API
-
When to Migrate from Cosmo OSS
Cosmo OSS offers a robust introduction to GraphQL Federation, enabling teams to manage complexity without commercial lock-in. As organizations grow, they may need Cosmo Enterprise, which enhances OSS with governance, observability, and dedicated support. This transition ensures operational efficiency and security, allowing businesses to scale confidently while protecting their infrastructure.
-
Safeguarding APIs: How K Health Ensures Security While Scaling with Cosmo
Originally published on WunderGraph TLDR; Challenge K Health needed a way to scale securely while keeping their microservices connected and API stable. Solution They adopted GraphQL Federation with Cosmo, leveraging schema checks to catch breaking changes early and hosting the router internally to maintain security and control. Results Queries now resolve more efficiently, reducing unnecessary…
-
SoundCloud and WunderGraph Cosmo Cut Computing Costs by 86%
SoundCloud optimized its GraphQL infrastructure by migrating to WunderGraph Cosmo. This switch cut costs by 86% and improved query latency by 45%, saving approximately $265,000 annually. The transition also enhanced performance and developer efficiency, allowing SoundCloud to build a leaner, scalable system, facilitating faster feature delivery while avoiding restrictive licensing.
-
From Custom Code to Cutting-Edge: On The Beach Adopts WunderGraph Cosmo for GraphQL Federation
On The Beach faced scalability issues with its monolithic GraphQL API as post-COVID travel demand surged. They transitioned to WunderGraph Cosmo, which streamlined federation management and improved developer workflows. The implementation enhanced performance, reduced operational costs, and allowed teams to innovate faster, positioning On The Beach for future growth in the travel industry.
-
Is gRPC Really Better for Microservices Than GraphQL?
The blog compares gRPC and GraphQL for microservices communication, focusing on performance versus flexibility. gRPC excels in performance with low-latency and binary serialization, ideal for backend interactions. In contrast, GraphQL offers flexibility in data retrieval with dynamic queries, better for client-driven applications. Both have advantages and can be integrated for optimal results.