Eliminating cold starts with Cloudflare ...
I just read this article https://blog.cloudflare.com/eliminating-cold-starts-with-cloudflare-workers/
Can I get some clarification? If I have a worker that will match on this for example
In my case I am using TRPC inside my worker, so it will handle some routing when it recieves the request. Another question is if I follow the first pattern and match that way, can I still use paths as long as they get handled internally in my worker?
Can I get some clarification? If I have a worker that will match on this for example
auth.development.example.com instead of only matching on development.example.com/auth* Cloudflare can improve or eliminate the cold start. Is this correct? In my case I am using TRPC inside my worker, so it will handle some routing when it recieves the request. Another question is if I follow the first pattern and match that way, can I still use paths as long as they get handled internally in my worker?
The Cloudflare Blog
A “cold start” is the time it takes to load and execute a new copy of a serverless function for the first time. It’s a problem that’s both complicated to solve and costly to fix.
