Routing tier for highly-available applications on a multi-tenant platform-as-a-service (PaaS) system
Implementations of a routing tier for highly-available applications on a multi-tenant Platform-as-a-Service (PaaS) system are disclosed. A method of the disclosure includes receiving, from a broker of a multi-tenant PaaS system, information related to a load balancer gear of an application running on the multi-tenant PaaS system. The information includes endpoint information indicating a location of the load balancer gear, and cartridge information identifying one or more cartridges implemented on the load balancer gear. The method further includes updating a routing table in view of the endpoint information and the cartridge information, and causing traffic to be routed to the load balancer gear in view of the updated routing table. The load balancer gear directs traffic to one or more other gears of the application.
1. A method, comprising:
receiving information related to a load balancer gear of an application running on the multi-tenant Platform as a service (PaaS) system, wherein the information comprises endpoint information indicating a location of the load balancer gear, and cartridge information identifying one or more cartridges implemented on the load balancer gear;
updating, by a processing device, a routing table in view of the endpoint information and the cartridge information; and
causing traffic to be routed to the load balancer gear in view of the updated routing table regardless of whether a previously-utilized load balancer gear of the application is operational, the load balancer gear to direct the traffic to one or more other gears of the application.
2. The method of claim 1 , further comprising:
causing additional traffic to be routed to the previously-utilized load balancer gear of the application, wherein the additional traffic was previously routed to the previously-utilized load balancer gear prior to receiving the information related to the load balancer gear.
3. The method of claim 1 , further comprising causing the load balancer gear to route the traffic to a subset of a plurality of gears in view of the cartridge information.
4. The method of claim 1 , wherein the endpoint information comprises one or more of an endpoint domain name service (DNS) entry of the load balancer gear, a port number, a hostname of a host server of the load balancer gear, a protocol used by the gear, or a location of one or more backend gears.
5. The method of claim 4 , wherein the protocol used by the gear comprises one of Hypertext Transfer Protocol (HTTP), Hypertext Transfer Protocol Secure (HTTPS), Transmission Control Protocol (TCP), Git, Secure Shell (SSH), or a MySQL protocol.
6. The method of claim 1 , wherein the load balancer gear and the previously utilized load balancer gear each reside on different nodes of the multi-tenant PaaS system.
7. A non-transitory machine-readable storage medium including instructions that, when accessed by a processing device, cause the processing device to:
receive information related to a load balancer gear of an application running on the multi-tenant Platform as a Service (PaaS) system, wherein the information comprises endpoint information indicating a location of the load balancer gear, and cartridge information identifying one or more cartridges implemented on the load balancer gear;
update, by the processing device, a routing table in view of the endpoint information and the cartridge information; and
cause traffic to be routed to the load balancer gear in view of the updated routing table regardless of whether a previously utilized load balancer gear of the application is operational, the load balancer gear to direct the traffic to one or more other gears of the application.
8. The non-transitory machine-readable storage medium of claim 7 , including instructions that, when accessed by the processing device, cause the processing device further to:
cause additional traffic to be routed to the previously-utilized load balancer gear of the application, wherein the additional traffic was previously routed to the previously-utilized load balancer gear prior to receiving the information related to the load balancer gear.
9. The non-transitory machine-readable storage medium of claim 7 , wherein the instructions further cause the load balancer gear to route traffic to a subset of a plurality of gears in view of the cartridge information.
10. The non-transitory machine-readable storage medium of claim 7 , wherein the endpoint information comprises one or more of an endpoint domain name service (DNS) entry of the load balancer gear, a port number, a hostname of a host server of the load balancer gear, a protocol used by the gear, or a location of one or more backend gears.