A few days ago, I launched the “Load Balancing” Node: https://steem.justyy.workers.dev

It is a Javascript code that runs on the CloudFlare edges (more than 200 network centers). The network is the computing. When requests are received, the Node will send a ‘ping’ request to a few nodes, and whoever returns first win the request.

See this on the CloudFlare worker debugging console – the remote virtual debugger.

But all those work are behind the scenes. The user will not see these details, and the Load Balancer is just working fine – and it indicates the actual Node that served the requests via the Response’ custom header `origin`

It is a perfect use case to let the CloudFlare workers handle the Load Balancing and route the traffic to the fastest server. The serverless technology is cost-effective (no need to pay for the servers), secure (patches are applied/installed automatically), hassle-free (you don’t manage the servers) and fast i.e. the Workers run on the Cloudflare Networks (more than 100 countries and 200 network centers – usually mean shorter pings).

Free plans are limited to 10ms CPU time per worker script, 30 workers, and 100K requests per day. Worker unlimited are limited to 50ms, and 10 Million requests per month (always shortest latency to worker nodes)

–EOF (The Ultimate Computing & Technology Blog) —

推荐阅读：
How to Sort Integers by The Number of 1 Bits?　 Using Depth First Search Algorithm to Delete Tree Nodes with Sum　 Web Strategies to Start Your SEO Journey　 How to Compute the Product of Last K elements in Array using the　 How to Write a High-Quality Blog Post in Just 30 Minutes　 8 Things To Include In Your Blog Privacy Policy　 Customer Success Strategy: 7 Reasons Why You Need One for Your B　 Tips On Creating Content For Marketing For 2020　 Best Image Optimizer Plugins for WordPress in 2019　 A Blogger’s Guide to Successful Content Marketing in a Saturated