{"id":1510,"date":"2018-08-01T14:52:48","date_gmt":"2018-08-01T13:52:48","guid":{"rendered":"https:\/\/www.lightsoftai.com\/?page_id=1510"},"modified":"2018-08-03T12:30:21","modified_gmt":"2018-08-03T11:30:21","slug":"loadbalancer","status":"publish","type":"page","link":"https:\/\/www.lightsoftai.com\/?page_id=1510","title":{"rendered":"Loadbalance with failover protection"},"content":{"rendered":"\n

Your company have been using services on a single server. And now it has come to a point, where you need to have multiple services, and even maybe introduce HTTPS but don’t own a certificate.<\/p>\n\n\n

\n
\"\"<\/a>
Are your solution made like this?<\/figcaption><\/figure>\n<\/div>\n\n

\u00c2\u00a0<\/p>\n

When the demand on services are increasing, the possibility to expand the servers also arise. By distribute the traffic internally is sometimes costly for small\/medium companies. Hardware is expensive and not all is supporting the external communication of encryption with HTTPS without a certificate and still use the unencrypted traffic internally.<\/p>\n

By using 2 loadbalancers, a primary and secondary (as a backup if primary stops working), they will handle frontend requests and pass them to backend servers, with either sticky sessions so that same client will use same backendsystem, or roundrobing.
Loadbalancer will also hold responsible for HTTPS Certificate and decrypt and pass the request to backends.<\/p>\n\n\n

\n
\n