Happy New Year! To kick off 2020, we’re proud to announce Kuma’s 0.3.2 release that includes long, anticipated features. The most prominent one is Kong Gateway support for ingress into your Kuma mesh. Another exciting feature that was widely requested is Prometheus support, which will enable you to scrape your applications’ metrics. Lastly, we announced the Kuma GUI in the last release. Thanks to a lot of early feedback, we’ve added many exciting improvements in this release.
Editor's note: Today’s post comes from Surin Asawachaisittigul, head of open APIs at Krungsri Consumer a subsidiary of Krungsri Bank, the fifth largest bank in Thailand, and focuses on personal loan and credit card services. Using APIs, Krungsri Consumer is taking an established bank into the digital future of finance. The finance industry is changing quickly in the digital age. Customers no longer want to pay for purchases in cash.
As some of you already know, I have been following the shift towards microservices adoption for a while now. For the longest time, when the industry thought of the transition to microservices, they thought of smaller companies leading the charge. However, I’ve seen large enterprises get value from microservices as well and saw this trickle-in starting in 2016, which is why I am excited to learn this now has achieved mainstream adoption.
Kong for Kubernetes (Kong for K8S) is a Kubernetes Ingress Controller based on the popular Kong Gateway open source project. Kong for K8S is fully Kubernetes Native and provides enhanced API management capabilities. From an architectural perspective, Kong for K8S consists of two parts: A Kubernetes controller, which manages the state of Kong for K8S ingress configuration, and the Kong Gateway which processes and manages incoming API requests.
Welcome to another hands-on Kuma guide! In the first guide, I walked you through securing an application using Kuma in a Kubernetes deployment. Since Kuma is platform-agnostic, I wanted to write a follow-up blog post on how to secure your application if you are not running in Kubernetes. This capability to run anywhere differentiates Kuma from many other service mesh solutions in the market.
It's a fact of modern software development that aspects of our applications interact with third-party APIs. This could be for any number of reasons, with some common ones being payment processing, telecommunications, logging, and data analysis. So, since our applications rely upon third-party APIs so much, we need to ensure that we integrate with them as effectively — and defensively — as we can.
