What Is Serverless Scripting?
To activate serverless scripting you will need to first make sure you have our CDN service enabled, which you can simply do by purchasing CDN on its own, or within one of our edge delivery stacks (recommended).
Why Use Serverless Scripting?
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 Serverless Scripting Not?
Serverless scripting 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:
- Serverless scripting is not a replacement for or alternative to the StackPath CDN. CDN service is required to run serverless scripts.
- Serverless scripts live and die per request; the code is not continuously running in the background.
Updated about 3 years ago