With trends moving to Serverless or Function-as-a-Service we've started building our web servers from instances of Express running inside Docker containers, to "functions" that instead run on managed infrastructure, responding to each request as they arrive. Many cloud providers supply this type of system which is fast, cheap, and very easy to maintain as all you have to do is upload your functions. Cloudflare in particular innovate further by replicating your worker to every edge node in their network, drastically limiting CPU + memory time, in exchange for response time as each worker 'instance' is located physically close to users. With previous approaches, worker instances were usually just located in a single region with redundant zones only; thus requiring a load balancer to be setup which is also not simple. Read more...

Comparing how each of the leading CDN providers do in CORS testing. Read more...

Using content distribution networks (CDNs) to globally distribute static assets for your website or web appoication, such as it's images, JavaScript files, videos and downloads etc, is increasingly common. It's common because they are reliable systems, cheap to use, easy to get setup on, and take a chunk of work off developers from having to build and maintain these systems themselves. I've devised a list of seven tips and best-practicies to look out for when picking which company should be your CDN provider. Read more...