Health Check Backup Origin
ORIGIN SERVER AND LATENCY ON ORIGIN SERVER
In a nutshell, the term “origin server” is used on behalf of the original content owner that responds to incoming requests by forwarding the content of the website. Once a client (i.e., content consumers, us) requests content through their browsers, relevant content is transferred by the origin server. Consequently, an inevitable delay called round-trip time (RTT) occurs, which is caused by the natural flow of Internet packets in our digital world. However, holding RTT at a minimum level is in our hands. To be more precise, the amount of traffic due to the increase in the number of incoming requests is one of the main reasons for the excessive RTT values. If content providers’ origin servers can not handle such a huge demand due to their limited capacity, it causes lasting downtimes and low quality of service (QoS) scenarios. Today’s content providers like e-commerce sites, online education platforms, or even blog sites suffer from irrepressible RTT durations. The solution is simple. Origin Shield, Backup Origin Server, and Health Check Backup Origin are the most effective solutions to these problems.
“Origin shield” is a layer between CDN and origin server formed by caching content to defend the origin server from overloading. As the name implies, “origin shield” acts as a protector placed right before the origin server. The origin shield is the first line of defense, shielding the origin server from potentially millions of individual requests. Origin shield caches and serves the content itself; thus, preventing the origin server from being down, increasing the cache-hit ratio, and providing faster delivery. In other words, much higher performance and high-speed transmission become possible. At the same time, caching creates an alternative solution in case of malfunctions and disruptions in the origin server. Accordingly, it provides sustainability and robustness along with high speed and performance.
BACKUP ORIGIN SERVER
The Circuit Breaker is used to detect any fault and aims to prevent recurring faults continuously during maintenance. In case of any problem in the primary origin server, the incoming request is forwarded to the backup origin server thanks to the Circuit Breaker. As long as the problem persists, the backup origin server takes over and acts as the primary origin server until the problem with the primary origin server is fixed.
The load on the primary origin is redirected for backup when the primary origin server fails. All approved content is cached. It is possible to cache from primary and backup origin servers. Thus, the content is pulled from the backup origin shield server if the primary origin server fails.
When the problem is fixed, requests are redirected back to the primary origin server. In this way, if there is a problem with the primary origin server, there will be no interruptions or disruptions.
Fig 1. Customer Origin Primary is working fine. Fig 2. Customer Origin Primary has any problems.
ORIGIN SERVER HEALTH CHECK
The health check method sends specific requests at preset intervals and constantly monitors the status of the origin server. Monitoring the origin server enables redirecting to the backup origin in case of any failure or problem. In this way, a much faster solution process becomes possible.
It also performs a load balancing health check. In case of an overload on the origin server, the load balancer stops sending requests to the origin server and prevents the origin server from being overloaded.
At Medianova, we have engineered three solutions to accelerate, enhance and secure your content delivery. With Medianova Origin Shield, Health Check, and Backup Server technologies, we let you take control of your dramatically growing content demand depending on your business needs. We are always looking for optimized and autonomous ways to shape our systems. We care for data, and we know the value of data. Get in touch with us to learn more about how Medianova can help you deliver the best online experiences.