Deploy Your Upstreams on Server Nodes
Upstream provides the actual business logic and data for your APIs. They need to be deployed and configured before being integrated with the API gateway.
Prerequisites
- Learn key concept Upstreams.
Upstream Deployment
Upstream can be deployed in different options:
- Virtual machines - Deploy service binaries/packages on VMs directly
- Containers - Package services as Docker containers and deploy on orchestrators like Kubernetes
- Serverless - Develop functions and deploy on platforms like AWS Lambda
- On-premise - Host services on existing on-premise infrastructure
Consider factors like scalability, availability, and portability when choosing a deployment option.
Define Endpoints
Once deployed, the upstream must be configured with network endpoints that the API gateway can route requests to.
Virtual Machines
Assign public IP addresses and open ports on VM firewalls for service endpoints.
Containers
Use Kubernetes Ingress or LoadBalancer services to expose endpoints.
Serverless
Most serverless platforms automatically assign invoke URLs for functions.
On-premise
Define URLs or IPs with ports for on-premise services, and allowlist gateway IPs.
Service Discovery(Optional)
Service discovery mechanisms like Consul, Eureka can be used to dynamically detect service endpoints.
Health Checks(Highly Recommended)
Configure health check endpoints for services to allow gateways to detect availability and route traffic accordingly.