Create a Developer Platform
Rapidly design, publish and consume APIs and services
Is Your Developer Platform a Roadblock to Innovation?
Organizations embracing distributed architectures risk slowing development velocity, increasing management overhead and reducing service discoverability due to their legacy API platforms. Legacy solutions lack CI/CD integrations, cannot deploy natively on Kubernetes, and don’t provide visibility into services, minimizing the benefits of distributed architectures.
Slowed Development Velocity
Legacy API platforms fail to ensure consistent documentation, resulting in poor service discoverability and outages when docs do not match production.
Tedious Manual Processes
Legacy API platforms lack robust integrations with leading CI/CD tools, reducing ability to automate manual tasks and draining developer productivity.
Increased Risk of Disruptions
Legacy API gateways are not container- or kubernetes-native, creating risk of configuration drift due to separate management of the gateway and the underlying platform.
Reduce Deployment Risk
Eliminate risk of configuration drift by declaratively configuring Kubernetes and the Kong Gateway within a single YAML file. Limit who can make configuration changes through Role-based Access Controls (RBAC).
Boost Developer Productivity
Provide a frictionless onboarding and service discovery experience to drive API consumption. Ensure developers always have access to the most up-to-date documentation with automatic updates.
Accelerate Time to Market
Automate workflows and reduce manual tasks by seamlessly integrating with leading CI/CD tools. Automatically generate configurations and publish REST, GraphQL, and gRPC services to the Kong Dev Portal using Kong Studio.
MS3 Selects Kong Mesh to Power its Next-Generation Integration Platform
Yahoo! Japan - Looking Beyond the API Platform
Verifone Trusts Kong for its Global, Omnichannel Payments Solution
Papa John’s Accelerates Time to Market 3X with Kong
“Our customers want to provide the best possible experience for their customers, and being agile and able to rapidly improve their software is critical to that,” said Aaron Weikle, CEO of MS3. With more of its businesses moving digital, MS3 needed a simple way to address cross-cutting concerns such as encryption, identity and tracing to accelerate the building of new cloud native applications using containers and Kubernetes.
MS3 selected Kong Mesh to form the backbone of its new Enterprise Integration Platform. While other service meshes provided part of the solution with handling Kubernetes workloads, they fell short on their support for the virtual machines that form the bulk of MS3’s enterprise customers workloads.
Being able to inject end-to-end security and tracing without introducing performance issues is huge for our customers. With Kong Mesh and Kong, we know that our customers will get a flexible, high-performance solution for all their needs, now and in the future.Aaron Weikle, CEO at MS3
Innovation is at the core of Yahoo! Japan’s DNA. With its shift to microservices and an API-centric architecture, Yahoo! Japan needed more than just a gateway – it needed a true, high-performance platform built for centralizing and managing APIs across a modern architecture.
“We moved rapidly towards microservices over the past few years, and we needed to centralize our APIs,” said Kanaderu Fukuda. With Kong as a single point for proxying and routing traffic across all its API endpoints, Yahoo! Japan was able to centralize authentication and authorization functionalities.
With Kong, we knew that we would get something that would work perfectly with our technology today and set us up for where we want to go. Kong allows us to deploy on-premise, easily integrates with all the technologies we use across the company and gives us the flexibility we want to avoid vendor lock-in.Kanaderu Fukuda, Senior Manager at Yahoo! Japan
Verifon needed to streamline a large-scale, complex global payments system without disrupting services for global customer and merchant base. This posed a challenge for the global architecture team at Verifone since ecommerce and physical payments are traditionally supported by completely different systems.
Initially, the team at Verifone liked Kong because of its lightweight API gateway and the company’s focus on microservices. “As we learned more, Kong really stood out for being able to support lots of use cases.” said Hans van Leeuwen, Lead Architect at Verifone. “Kong’s flexible plugin architecture meant we could pick and choose the functionality we needed for each use case.”
With the number of new services we’re adding and creating from decoupling legacy applications into microservices, manually managing our infrastructure would be nearly impossible. Using Kong with Kubernetes allowed us to make decentralization a reality.Jason Walker, Senior Enterprise Architect at Cargill
In the fast-evolving retail and restaurant marketplace, consumers are discovering and engaging with restaurants in a variety of formats and on a variety of devices. With integration to aggregators and other emerging channels representing a critical business opportunity for Papa John’s, refining the API strategy became a priority for the company’s technology team.
Papa John’s chose Kong Enterprise as the service connectivity platform, including developer portal and integrations to CI/CD pipeline. Commerce Platform Team is at the center of the technology strategy for tapping into innovation wherever it resides, with integrations to various store, digital, and partner channels.
As these integrations scaled up, the addition of a robust API Gateway solution like Kong to our technology stack was a no-brainer.Sarika Attal, Senior Director at Papa John’s