The latest news and announcements about Kong, our products, and our ecosystem, as well as voices from across our community.
We are in the midst of an explosion of APIs and microservices. For some, the first instinct of creating an API is to get down to building one. Some level of planning will help manage the quality of APIs when working within a team. In this series of blogs, we will be sharing some…
There is a great number of logging plugins for Kong , which might be enough for your needs. However, they have certain limitations: Zipkin is a tracing server, specialized in gathering timing data. Used in conjunction with Kong's Zipkin plugin , it can address the points above: For a basic setup,…
Today, we're thrilled to announce the release of a major expansion to the Insomnia family of open source developer tools — Insomnia Designer ! Providing a collaborative environment for editing GraphQL and REST APIs, Insomnia Designer allows developer teams to more easily embrace spec-first…
Today we’re thrilled to announce a brand new product area for Kong – Kong Studio, an integrated design and test environment for Kong Enterprise customers. We are excited to make the leap in extending our service control platform to include pre-production use cases focused on improving the way that…
API Fortress is a continuous testing platform for APIs. We've been a friend to Kong since the beginning. In this guest blog post, we explain how our company uses Kong to facilitate the process of virtualizing APIs. As more companies adopt microservice architectures and DevOps best practices, APIs…
Want to take your API to the next level? Then you should give your API an OpenAPI spec! An OpenAPI spec is more than just documentation — with it, you can leverage your API to generate client code, do automated testing and more! During Kong Summit, Wordnik Founder Erin McKean gave an overview of…
Over the past few months, you may have noticed the explosion of industry chatter and articles surrounding service mesh and the future of software architecture. These discussions have been highly polarizing, with tribes forming around specific vendors. While this partisan trend is to be expected,…
This is the second of two blogs examining considerations for transitioning to a microservices-based architecture. For more information, check out our e-book Blowing Up the Monolith: Adopting a Microservices-Based Architecture . In our previous blog, we outlined the five questions we must consider…
Secure your AI infrastructure with prompt guards, PII sanitization, and centralized governance. Control LLM costs with token-based rate limiting and semantic routing across providers.