We’re seeing a massive shift in how companies build their software. More and more, companies are building—or are rapidly transitioning—their applications to a microservice architecture. The monolithic application is giving way to the rise of microservices. With an application segmented into dozens (or hundreds!) of microservices, monitoring and consolidated logging become imperative.
We are now deep into our most anticipated event of the year, Kong Summit 2021 (there’s still time to register for Day 2!). More than 4,000 people have registered from 87 countries for the virtual event. After a full day of knowledge and surprises, we are excited to recap the most memorable moments from today.
Today at Kong Summit, we are thrilled to announce several new products, features and capabilities across our entire service connectivity platform with the goal of making service connectivity as invisible and easily consumable as electricity. These updates include making the Kong Istio Gateway integration generally available and debuting Insomnia Projects. We’re excited to share them with you all.
Let’s face it: In today’s modern world of cloud and containers, there are still thousands of legacy applications that were not written with an API-first approach. Some legacy systems can still provide tremendous value today, but the means for accessing them are completely out of date, thus rendering them almost useless.
While monitoring is an important part of any robust application deployment, it can also seem overwhelming to get a full application performance monitoring (APM) stack deployed. In this post, we’ll see how operating a Kubernetes environment using the open-source Kong Ingress Controller can simplify this seemingly daunting task! You’ll learn how to use Prometheus and Grafana on Kubernetes Ingress to simplify APM setup.
As the software application world moves from monolith architectures to microservices, we are also seeing a shift toward developing modular and reusable APIs. According to APIOps, reusable APIs are consumable APIs, which means they must be well-documented and compliant. The separation between the designers, builders and consumers of an API grows larger and larger, making the API specification even more central to that API’s success.
Automating digital transformation API deployments can help speed time to market and minimize the resources required for the deployments — if developers can be assured that the automated process meets all necessary security requirements. It’s a topic that Kong Senior CustomerExperience Manager Peggy Guyott and Kong Senior Solutions Engineer Ned Harris discussed on a recent webinar as part of the Destination: Automation 2021 digital event.
Event hooks are a brand new feature we launched with Kong Gateway 2.5 that allows you to get notifications when certain events happen on your Kong Gateway deployment. If you want to keep an eye out for when your system creates new administrators or adds new plugins to a latency-sensitive route, this is the feature for you! Event hooks is a Kong Gateway Enterprise feature. Interested in learning more? Contact our sales team.
As more and more companies move to a multi-cloud strategy and increase usage of a cloud native infrastructure, API providers are under a lot of pressure to deliver APIs at scale in multi-cloud environments. At the same time, APIs should follow each company’s security requirements and best practices, no matter the cloud platform. These reasons explain why many providers have such complex API authorization requirements.
Just under one year ago, we launched version 1.0 of our Kong Ingress Controller (KIC). That was a huge milestone for us here at Kong, and we know it was for you – Kong Nation – as well. Since then, with the help of our community, we’ve merged over 300 new features and bug fixes and have started to enter a new era of KIC: version 2.0. Prior to releasing KIC 2.0, we want to make sure to incorporate community and customer feedback, so we are announcing the KIC 2.0 Beta.
