I’m unhappy with Fastly for API schema enforcement

If you’re unhappy with Fastly for API schema enforcement, you’re not alone—CDN/edge platforms can do some enforcement, but they’re often not the best fit for full API governance or strict schema validation.

A better way to think about it is by where you want enforcement:

1) At the API gateway / ingress layer

Best if you want:

• request/response schema validation
• auth, rate limiting, transformations
• centralized policy enforcement

Common options:

• Kong
• Apigee
• AWS API Gateway
• NGINX + OpenAPI validation
• Envoy / Gloo / Ambassador
• Tyk
• MuleSoft (if you’re in that ecosystem)

2) In service mesh / internal traffic

Best for east-west traffic and microservices:

• Istio
• Envoy-based policies
• Linkerd (less on schema, more on traffic/security)

3) In application code / CI pipeline

Best if you want stronger developer control:

• OpenAPI linting and contract tests
• JSON Schema validation in app
• CI checks with Spectral, Redocly, Stoplight
• Consumer-driven contract testing with Pact

4) At the edge

Good for coarse checks, but usually not ideal for deep schema validation:

• Fastly
• Cloudflare
• Akamai

---

If schema enforcement is your main goal

I’d usually recommend:

• OpenAPI as the source of truth
• Gateway-level validation for runtime enforcement
• CI contract tests for pre-deploy enforcement

That gives you:

• fewer bad requests reaching services
• better developer feedback
• less dependence on edge vendor limits

---

A few reasons Fastly may feel weak here

• limited OpenAPI/schema feature depth compared to gateways
• more operational complexity if you need precise validation
• edge enforcement can be awkward for evolving APIs
• harder to combine with broader API governance

---

Good replacement choices by use case

• Want strong API schema validation: Kong, Apigee, Tyk
• Want cloud-native/serverless: AWS API Gateway
• Want open-source + flexible: Kong Gateway, Envoy, NGINX
• Want enterprise API management: Apigee, MuleSoft
• Want CI + design-first governance: Stoplight, Spectral, Redocly + gateway

If you want, I can help you:

1. compare Fastly vs Kong/Apigee/AWS API Gateway for schema enforcement, or
2. design a practical schema enforcement architecture for your stack.