In the age of surgical robots, smart refrigerators, self-driving vehicles and unmanned aerial vehicles, connectivity undoubtedly is a foundational block for our modern world. Connectivity not only enables easy access to resources, but it also opens up opportunities to drive innovation by connecting isolated systems. Connectivity drives digital transformation.
We are happy to announce a new major release of Kuma, and a new major release of Kong Mesh built on Kuma! Kuma 1.2 ships with 20 new features and countless improvements. We strongly suggest to upgrade, in order to take advantage of the latest and greatest when it comes to service mesh.
Kong Developer Portal comes out of the box with a RESTful API-based catalog and YAML-based template functionality. In this tutorial, I’ll show you how to get to the next level of API documentation using Kong Developer Portal with GraphQL. That way, you’ll be able to give your API developers an interactive experience.
In our third Kong and Okta tutorial, we’ll go through the introspection flow implementation. This series will show you how to implement service authentication and authorization for Kong Konnect and Okta using the OpenID Connect (OIDC) plugin.
Razorpay is a payments processor that’s required to comply with PCI guidelines. This article will explain how we developed a custom Lua plugin to simplify PCI compliance with Kong Gateway.
The demand for digital transformation has accelerated, with 62% of technology leaders sharing that they fear they are at risk of being displaced by competitors who innovate more quickly. Enterprises are increasingly transitioning from monolithic to microservices architecture, with the goal to accelerate application development, speed up innovation and reduce time to market.
One of the most common questions I get asked is around the relationship between Kong Gateway and Kuma or Kong Mesh. The linking between these two sets of products is a huge part of the unique “magic” Kong brings to the connectivity space. In this blog post and the video below, we’re going to jump right into breaking down the relationship between these products and how you can use them together. First, let’s break down a couple of the terms that are involved.
Multi-cloud infrastructure is changing the way companies approach their software architecture. What started solely as gateway traffic management has evolved into full lifecycle API management. I recently sat down with Reza Shafii, Kong’s VP of product, for a blog series where we explore how full lifecycle service management ties into the concept of cloud native.
Konnect is a hybrid cloud control plane managed by Kong that launched in May. Konnect provides an easy way to create and configure service configurations through a UI, rather than using the admin API and HTTP requests to configure your Kong Gateway. On top of that, it provides usage analytics, a developer portal and role-based access control for service configuration. If you have a Kong Gateway OSS installation, you may be wondering how you can move your instance over to Konnect.
Operating APIs and microservices at scale relies on the right processes and company culture. APIOps is the name for this overall approach. If done right, organizations can accelerate digital business with APIOps. It combines modern automation tooling with best practice engineering principles to ensure that the organization delivers with continuous quality as well as speed. In this blog series we explore the triggers for adopting APIOps, and its impact, through the story of “Acme.”
