<p>Our project is undergoing a refactor to a micro-services architecture, and we are currently considering different API gateway solutions.</p>
<p>We did our research, looked at the official sites for several solutions, went over some technical comparisons of different solutions, and read articles about our top picks.</p>
<p>So far our main contenders are <strong>Apachee APISIX</strong> and <strong>Kong</strong>, but we are quite torn between them and would like to get a general opinion from actual users.</p>
<p>Below are outlined the different properties and requirements of the project, I would appreciate it if any of you can point out some pros and cons of a solution you are familiar with in regard to them, and it would be great if someone facing similar requirements could share their experience with actually integrating one.</p>
<p><strong>General Info</strong></p>
<ul>
<li>The project is of medium scale, has an active user base, and sees daily use around the clock with an incoming traffic count of a few thousand per minute on the backend.</li>
<li>The project is hosted in a private network, and no cloud services are utilized, so we are looking for a good on-prem solution.</li>
<li>Looking for a rather lightweight solution.</li>
</ul>
<p><strong>Technical Info and Requirements</strong></p>
<ul>
<li>AD FS-based authentication.</li>
<li>Significant reliance on JWT.</li>
<li>Using WebSocket in some micro-services, specifically Socket.io.</li>
<li>Kubernetes deployment, supported by Helm.</li>
<li>Full-stack under Monorepo.</li>
<li>Repository and CI/CD are hosted and managed on GitLab.</li>
<li>The team is trained in several coding languages but prefers working mainly with Typescript as we use React for the front-end, and NestJS for the back-end.</li>
</ul>
<p>Thank you!</p>

Onlu
<p><strong>Apachee APISIX</strong> and <strong>Kong</strong> both are good at first place. i would suggest better to go depending on the <strong>use case</strong> which resolves for you.</p>
<p>Coz when you say <strong>JWT</strong> both might be supporting the plugin or JWT option but would you like to parse <strong>JWT</strong> before the request reaches to service, header modification ?</p>
<p>In the above case, you might be having an already existing plugin but not with other.</p>
<p>Do you have any requirement for a <strong><a href="https://github.com/pantsel/konga" rel="nofollow noreferrer">UI dashboard</a> (Admin API)</strong> for <strong>Kong</strong> there is an open source available but i am not sure about <strong>APISIX</strong>.</p>
<p><strong>Apachee APISIX</strong> is good for the <strong>cloud native</strong> while <strong>Kong</strong> is battle tested widely used.</p>
<p><strong>Kong</strong> is a <strong>feature</strong> rich API gateway with Wide community while other side Apache <strong>high-performance</strong> gateway with <strong>plugin</strong> support.</p>
<p>This is my old article on Gateway comparison : <a href="https://medium.com/@harsh.manvar111/api-gateway-identity-server-comparison-ec439468cc8a" rel="nofollow noreferrer">https://medium.com/@harsh.manvar111/api-gateway-identity-server-comparison-ec439468cc8a</a></p>
<p>you can see <strong>Kong</strong> is good, personally, i have used and satisfied my team's requirements with minimal effort.</p>
<p>You can read my few articles on <strong>Kong</strong> and how it's easy to set up <strong>Kong</strong> with <strong>UI dashboard</strong> to manage</p>
<ul>
<li><a href="https://medium.com/faun/securing-the-application-with-kong-keycloak-101-e25e0ae9ec56" rel="nofollow noreferrer">https://medium.com/faun/securing-the-application-with-kong-keycloak-101-e25e0ae9ec56</a></li>
<li><a href="https://medium.com/faun/kong-jwt-scope-base-auth-with-keycloak-b9938a96d281" rel="nofollow noreferrer">https://medium.com/faun/kong-jwt-scope-base-auth-with-keycloak-b9938a96d281</a></li>
</ul>
<p>But again Apachee APISIX is also good to choose wisely based on your actual <strong>use case</strong> and requirement.</p>
