APIs are increasingly critical to many businesses, so choosing the right API gateway pattern for your application delivery infrastructure is key. Here we explore five such patterns: edge gateway, two-tier gateway, microgateway, per-pod gateways, and sidecar gateways.
The NGINX Application Platform accelerates application delivery from code to customer with a comprehensive API delivery solution that spans from creation of API functions through their delivery to end users. Step-by-step instructions for configuring NGINX Controller and NGINX Unit are provided.
We examine the state of API gateways as the industry transitions from monolithic to microservices‑based apps, considering the challenges of hugely distributed app environments. We explore the role of API gateways in a service mesh and in hybrid clouds.
PingIdentity provides an NGINX integration with its AI-driven solution for API security, PingIntelligence for APIs. The solution uses API metadata collected by NGINX to determine whether API clients are granted access. PingIntelligence for APIs also provides dashboards, reports, and anomaly detection.
Your APIs need the same level of security, scalability, and visibility as your web applications. API gateway functionality is built into NGINX Plus, together with its many other high-performance features. NGINX Controller manages your API gateways and provides full API lifecycle management.
In this inaugural post in our "Ask NGINX" series, we explain how to convert F5 BIG-IP iRules and Apache rewrite rules to NGINX syntax, use NGINX as an API gateway and NGINX Controller for full API lifecycle management, and implement blue-green deployment with NGINX.
In his session at NGINX Conf 2018, Timo Stark of Audi shares how his team built the Audi Cockpit, a dashboard on which Audi employees access work apps. NGINX Plus serves as API gateway for the dashboard, which uses AWS-hosted microservices in Kubernetes-managed containers.
NGINX Plus covers all API gateway use cases, from traditional monoliths to distributed microservices. No need for the separate microgateway that first-generation API management vendors have had to bolt onto their solutions to handle modern application architectures.