What is EdgeEngine?
Why use EdgeEngine?
How does it work?
When a user request comes into a StackPath data center and your code is executed in the V8 engine, your code is executing before StackPath's CDN cache or WAF services. This ordering means you have complete control over incoming requests before StackPath responds to them, and can manipulate (or block) requests before StackPath responds or they get to your origin server.
What is EdgeEngine not?
EdgeEngine gives developers incredible capability and flexibility to easily deploy serverless applications around the world, but there are still a few things it is not. To be clear and transparent about what those are, we thought we should list those here:
- EdgeEngine is not a replacement for or alternative to the StackPath CDN. CDN service is required to run EdgeEngine scripts.
- EdgeEngine scripts live and die per request; the code is not continuously running in the background.
To learn how to upload your first EdgeEngine script, please view our Getting Started with Edge Engine article.