An Integrated Blueprint from Kong and Apollo
Not a day goes by where the tech press fails to mention industry advancements in AI, connected devices, or personalization. Consumers can now use AI to create anything from digital illustrations to vacation ideas. At the core of these initiatives is one tried-and-true constant – APIs. If an organization cannot safely and securely deliver service updates across any number of interfaces, these modernization initiatives will fail to gain traction.
APIs are more heterogeneous than ever though. An enterprise considering incorporating gRPC APIs may still have legacy SOAP APIs in the mix. A new feature could require data from 20 different services – all of which are managed by different teams at different cadences using varying protocols. If a Product Manager wants to incorporate data from legacy APIs as well as new options like ChatGPT, how can API platform teams provide a standardized means to iterate, secure access, and scale all of them? And then how do they ensure that client teams can get the data they need in a self-service fashion?
Kong and Apollo are industry leaders in the API space. Our customers come to us with these very real problems everyday. The API ecosystem often positions REST and GraphQL as competing technologies, but they are highly complementary and are instrumental in developing a modern API platform that accomplishes the goals above. Through a balanced exploration of Kong’s perspective on flexible, heterogeneous API ecosystems and Apollo’s expertise in GraphQL, we’ve captured the vendor-neutral best practices that combine API management and GraphQL into a unified reference architecture for building and operating a modern API platform.
Learn more with our joint paper and reference architecture that shows how to:
- Leverage GraphQL and a supergraph as a new layer in the stack atop existing microservices and API management.
- Streamline the developer experience in building and consuming APIs.
- Ensure secure, efficient runtime connectivity and implement robust governance mechanisms with API management best practices.
Phil is a Director of Product at Apollo GraphQL with 20 years' experience in product and engineering roles building successful new products at startups and large enterprises.
Stay in our orbit!
Become an Apollo insider and get first access to new features, best practices, and community events. Oh, and no junk mail. Ever.
Make this article better!
Was this post helpful? Have suggestions? Consider so we can improve it for future readers ✨.