A DMZ – Demilitarized Zone – is a military term, roughly summarized, as an area between two adversaries established as a buffer in order to reduce, or eliminate, the possibility of further conflict. In networking, the term usually refers to an area that acts as a buffer between two segregated networks. Here is a simplified visualization.
We are happy to announce release 2.2 of our flagship open source API gateway! Those were some busy three months since the release of Kong Gateway 2.1! We have pushed a number of patch releases in the 2.1 series, we’ve had our first fully-digital Kong Summit, and of course, we’ve been very busy building new features that are now shipping in Kong Gateway 2.2!
Kong Enterprise is a service connectivity platform that provides technology teams with the architectural freedom to build, operate, observe, and secure APIs and services anywhere. From Kong’s inception, we’ve been aligned with Amazon Web Services (AWS), enabling our customers to quickly and efficiently deploy Kong on their AWS accounts. As companies move from monolithic to microservice applications and beyond, Kong helps teams manage this transition.
Creating an API contract and corresponding Kong service are often just the first steps in the API development process. More often than not, the upstream services that are invoked provide a different contract to the one presented to the API consumer. This is especially the case in larger organizations where enterprise applications offer their own out-of-the-box integration contracts. Likewise, you shouldn’t expose the complexity of your upstream systems to your API consumer.
Strapi is a headless CMS based on Node.js. Headless means that it makes all of its content available via an HTTP API, so you can easily build your user-facing frontend around it. Since it’s a fully-fledged CMS, it brings an administration frontend out-of-the-box, making publishing and maintaining content straightforward - even for those without a technical background. Since everything in Strapi works via an API, it’s perfect for Moesif API monitoring.
Application programming interfaces, or APIs, are how software talks to other software. They abstract the complexity of underlying systems so the systems can connect in novel ways even if they were never intended to interoperate. Consequently, APIs are key ingredients in both most modern digital experiences and the execution of many of today’s most exciting business opportunities.
Embedded dashboards are an easy way to share the insights you got from Moesif across your team and with your customers. You define metrics, build your dashboards, and then share them, filtered by company or user, inside your developer portal. From a technical point of view, they’re just websites that can be displayed inside an iframe somewhere on your web pages.
Moesif had the privilege of picking the brain of the expert who literally wrote the book on API Product Management. In a wide-ranging discussion with Dr. Amancio Bouza we found out what you should really care about as an API product manager, and it’s not what you may think (hint: see the title). We also cover pricing your API, how to become a better product manager and what books should be on your nightstand.
Today, we’re excited to announce a new research project we’ve been kicking around at Kong: Kong Embedded! If you’ve used the Kong Gateway before or heard us talk about it, one of the things we’re very proud of is that Kong Gateway uses a very small resource footprint. It’s a small download in size, is blazingly fast on even constrained hardware, and uses very little memory.
We are proud today to announce the future of service connectivity – Kong Konnect! Kong Konnect is the only full stack connectivity platform that is designed from the ground up for the cloud native era, delivered as a service. It accelerates the journey to microservices, secures and governs APIs and services, and it allows developers to rapidly design, publish and consume APIs and services. Konnect was built from the ground up with the unique needs of developers, architects and operators in mind.
About two and a half years ago, Kong first announced our Kubernetes Ingress Controller. We were stepping up to invest in the Kubernetes community by building a full-featured API gateway that operated in a Kubernetes-native way. Since then, we – as well as the rest of the broader Kubernetes ecosystem – have hit a number of additional milestones. Our Ingress Controller has run in tens of thousands of Kubernetes clusters, and we’ve continued to expand its functionality and stability.
Today we’re launching new names for some of our most popular API products. This is part of refreshing our outlook on the API space and our subsequent API lifecycle tools. We loved our old names, and know many felt the same. And yet, here we are to explain why we decided the progression was necessary.