<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Kong - Tag - Lorenzo's Blog</title><link>https://www.k8s.it/tags/kong/</link><description>Kong - Tag - Lorenzo's Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Sun, 08 Nov 2020 00:00:00 +0000</lastBuildDate><atom:link href="https://www.k8s.it/tags/kong/" rel="self" type="application/rss+xml"/><item><title>Kubernetes API Gateway</title><link>https://www.k8s.it/posts/kubernetes-apigw/</link><pubDate>Sun, 08 Nov 2020 00:00:00 +0000</pubDate><author>Lorenzo Girardi</author><guid>https://www.k8s.it/posts/kubernetes-apigw/</guid><description><![CDATA[<div class="featured-image">
                <img src="/images/kubernetes-apigw/Screenshot-2020-11-20-at-22.20.25-2.png" referrerpolicy="no-referrer">
            </div><p></p>
<p>It&rsquo;s time to talk about the API gateway.</p>
<p>In a modern infrastructure — especially in a microservices environment — you probably know what I&rsquo;m referring to. But it&rsquo;s worth being explicit about it:</p>
<blockquote>
<p>&ldquo;An API gateway takes all API calls from clients, then routes them to the appropriate microservice with request routing, composition, and protocol translation. Typically it handles a request by invoking multiple microservices and aggregating the results, to determine the best path.&rdquo;</p>]]></description></item></channel></rss>