Let me have some reference notes here in this blog for the best practices that can be followed with respect to the Kong API gateway and their Architecture Patterns.
Background
Kong’s overall infrastructure is composed of three main parts: NGINX provides protocol implementations and worker process management, OpenResty provides Lua integration and hooks into NGINX’s request processing phases, and Kong itself utilizes those hooks to route and transform requests.
Kong Architecture Patterns
- Simple Kong between client and upstream as 'a proxy'
- Kong and APIs behind a firewall for more control over the APIs
- Separate Kong Admin node for better security
- Multi-datacenter with Cassandra for high availability to achieve higher throughput
References:
https://docs.konghq.com/enterprise/0.32-x/kong-architecture-patterns/
https://konghq.com/blog/microservices-high-availability/
https://docs.konghq.com/enterprise/0.32-x/kong-architecture-overview/
https://www.codit.eu/blog/kong-the-upcoming-king-of-the-api-jungle/
https://medium.com/swlh/kong-api-gateway-zero-to-production-5b8431495ee
