Why should you care?

CloudVerse mobile app talks to one gateway instead of six internal microservice URLs.

See it live — copy this example

Use AWS/Azure/GCP free tier or local Docker/Kind. Sketches and YAML are meant to be typed and adapted.

# NGINX ingress + rate limit (CloudVerse)
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: cloudverse-api
  annotations:
    nginx.ingress.kubernetes.io/limit-rps: "100"
    nginx.ingress.kubernetes.io/auth-url: "https://auth.cloudverse.internal/validate"
spec:
  ingressClassName: nginx
  rules:
  - host: api.cloudverse.io
    http:
      paths:
      - path: /v1/payments
        pathType: Prefix
        backend:
          service: { name: payments-api, port: { number: 80 } }
      - path: /v1/orders
        pathType: Prefix
        backend:
          service: { name: orders-api, port: { number: 80 } }

What happened?

• Gateways centralize cross-cutting concerns.
• Avoid turning them into a second monolith with heavy aggregation logic.

Practice next

1. Route two paths to two services.
2. Add JWT validation at gateway.
3. Apply rate limit annotation.
4. Add canary weight split 90/10.
5. Expose OpenAPI spec at /docs via gateway.

Remember

Single client entry. Auth + limits at edge. Route to internal services.

CloudVerse mobile API

Public clients need throttling on login.

Outcome: Gateway rate limit blocks abuse before auth service.