Conceptually this is similar to how we use Fastly, using Varnish Configuration Language. Though I do appreciate the concept of using the same API at the edge compute node as well as on the browser.
I don't think these topics are super well understood, but dev.to is served from the edge, with some logic at that point, and then some more once the request hits the browser (service workers + local storage etc. to ultimately show the specific user their content as quickly as possible.)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Conceptually this is similar to how we use Fastly, using Varnish Configuration Language. Though I do appreciate the concept of using the same API at the edge compute node as well as on the browser.
Interesting.
Reading about Lambda@Edge and Cloudflare Workers just introdruced me to this concept :D
But, well, guess I'm a front-end dev by heart
I don't think these topics are super well understood, but dev.to is served from the edge, with some logic at that point, and then some more once the request hits the browser (service workers + local storage etc. to ultimately show the specific user their content as quickly as possible.)