Prompt
Fastly Compute@Edge is too complex for simple request routing
Latest observation
Nov 17, 2026
OpenAI APIWeb search: off
That’s a fair critique. Fastly Compute@Edge is powerful, but for simple request routing it can feel like overkill compared with more direct options.
Why it can feel too complex
- Requires writing and deploying code just to route or rewrite requests
- More moving parts than basic CDN rules or edge redirects
- Higher learning curve if you only need simple path/host-based routing
- Operational overhead from a full compute runtime when a small config would do
When it does make sense
Compute@Edge is better if you need:
- dynamic routing logic
- custom authentication or headers
- A/B testing or geo-based decisions
- request/response transformation
- integration with external services
If your need is simple routing
You may want:
- Fastly VCL for straightforward edge logic
- redirect/rewrite rules if available in your setup
- a simpler reverse proxy / load balancer layer
- platform-native routing tools from your hosting provider
Bottom line
If your goal is just “send /api here and /app there,” Compute@Edge may be more machinery than necessary. It’s best suited for more complex edge behavior.
If you want, I can help you compare Compute@Edge vs VCL vs simple routing rules for your specific use case.