In the last blog, we discussed the challenges in managing APIs at scale in a Kubernetes environment. We also discussed how deploying a Kubernetes Ingress Controller or an API gateway can help you address those challenges. In this blog, we will briefly touch upon some of the similarities and differences between an API gateway and Kubernetes Ingress. We will also discuss a unique approach offered by Kong for the end-to-end lifecycle API management (APIM) in Kubernetes.

The world of business is increasingly becoming more dependent on APIs. For companies looking to take advantage of the latest technologies to improve their own business, it makes sense to start building a solid framework around API. Here are 13 reasons why you should be investing in APIs for your business.

As APIs and microservices evolve, the architecture used to secure these resources must also mature. Utilizing a token-based architecture to protect APIs is a robust, secure and scalable approach, and it is also much safer than API keys or basic authentication. However, token-based architecture comes in varying maturity levels, as outlined by the API Security Maturity Model.

As Kong continues to expand its global footprint, we recently added Kore Labs, experts in FinTech digital product lifecycle management solutions, to the Kong customer community in the UK. Kore built its cloud-enabled solution on top of Kong in order to revamp its architecture to scale and provide customized solutions for its clients.

Customers today expect feature-reach and user-friendly access to technology that makes their lives easier. They expect to use this technology to engage with companies anywhere, anytime, and with any device. Organizations must be able to not just meet, but exceed, these expectations. Failing to do so could result in lost revenue as customers move on to competitors.

Unlike a traditional monolithic approach, in which all components form an inseparable entity, microservices work in synergy to accomplish the same tasks while being separate. Each of these components or processes is a microservice. Granular and lightweight, this type of software development allows a similar process to be used in multiple applications. This is a key element in optimizing application development for a cloud-native model.

One of the things that’s quite interesting about service mesh is that it has not been a very well-defined category for a very long time. Service mesh is not a means to an end. By looking at its adoption, we’ve been seeing a refocus on the end use case that service mesh allows us to enable. Some are around observability while others are around security and trust – being able to provide that identity to all of our services.

In our first episode of Kongcast, I had the pleasure of speaking with Liz Fong-Jones, principal developer advocate at Honeycomb, about the concept of error budgets for service level objectives (SLOs) and how to accelerate software delivery with observability. Check out the transcript and video from our conversation below, and be sure to subscribe to get email alerts for the latest new episodes.