We’re happy to announce the general availability of Kong Enterprise 3.2. In this release, we’ve taken significant steps to ensure the smooth and reliable operation of our API management solution. In Kong Enterprise 3.2, we’ve delivered key functionality for customers that operate Kong Enterprise in a hybrid environment in order to further enhance its reliability. Specifically, we’ve expanded Kong Enterprise’s capabilities in the following areas.
Red Hat OpenShift is the industry’s leading enterprise Kubernetes platform that runs ubiquitously across on-prem, and the cloud. With Red Hat OpenShift Service on AWS (ROSA), a managed Red Hat OpenShift platform that runs natively on AWS, it is even easier to get kick-started on an enterprise-ready instance of Red Hat OpenShift in the cloud. Kong similarly distinguishes itself as a multi-platform, multi-cloud API Management solution pushing the vision of APIs.
Developers will remember times when they were trying to figure out why something they were working on wasn’t behaving as expected. Hours of frustration, too much (or perhaps never enough) caffeine consumed, and sotto voce curses uttered. And then — as if by fate — the issue is narrowed down to a simple oversight that makes perfect sense upon discovery. Problem solved!
In this post, we’ll talk about what APISecOps is, including the fundamentals of it and the personas involved. Then, we’ll discuss how API, microservice, and policy lifecycles integrate to produce a secure service in production, and why collaboration and API-Design First are essential for APISecOps success.
Looking to develop more APIs faster (and securely)? Then you have some different API platform deployment models to consider. In this post, we’ll define and compare the siloed, centralized, and federated API platform deployment models — and dive into why federated API management is key to striking a balance between agility and governance.
