Making a Rails Health Check that doesn't hit the database

01-Sep-2016 3781

In a production application you usually have many servers, and each of those servers gets checked periodically to make sure they're still healthy and working as expected. When they are, requests can be routed at them by your load balancer. If a server doesn't respond to the healthcheck, then it is presumed to be dead or unhealthy, and requests are diverted to the healthy servers instead. If you've got an autoscaling solution set up, unhealthy servers can be killed, rebooted, and re-added to the load balancer's pool of healthy servers.

Use coupon code:

RUBYONRAILS

to get 30% discount on our bundle!
Prepare for your next tech interview with our comprehensive collection of programming interview guides. Covering JavaScript, Ruby on Rails, React, and Python, these highly-rated books offer thousands of essential questions and answers to boost your interview success. Buy our 'Ultimate Job Interview Preparation eBook Bundle' featuring 2200+ questions across multiple languages. Ultimate Job Interview Preparation eBook Bundle