GCP में नेटवर्क और HTTP (रों) लोड संतुलन के बीच मतभेद

Question

जीसीपी दो लोड बैलेंसर्स प्रदान करता है क्या हैं अर्थात् नेटवर्क और HTTP (रों) जहां परत 4 पर पूर्व काम करता है और परत पर बाद में काम करता है 7।

एक दस्तावेज भी है जो बताता है कि यहां तक ​​कि HTTP ट्रैफ़िक को नेटवर्क लोड बैलेंसर द्वारा संतुलित किया जा सकता है। यह थोड़ा उलझन में है कि जीसीपी में वेब ऐप के लिए कौन सा लोड बैलेंसर चुनना है। परियोजना के लिए एक चुनने से पहले मतभेदों को समझना बेहतर है।

मैं उन दोनों के बीच मतभेद कार्यप्रवाह, सेटअप, क्षेत्र/क्षेत्र आधारित, सत्र आत्मीयता और कई अन्य के लिए विकल्पों के आधार पर पता करने के लिए करना चाहते हैं।

Answer 1

बनाम HTTP (रों) लोड बैलेंसर

+---------------------+------------------------------------------+------------------------------------------------------+ 
|  Category  |  Network Load Balancing (NLB)  |    HTTP(S) Load Balancing (HLB)    | 
+---------------------+------------------------------------------+------------------------------------------------------+ 
|  1. Region/ | NLB supports only within a region.  | HLB supports both within cross-region    | 
|  Cross-Region | Does not support cross-region   | load balancing.          | 
|      | load balancing       |              | 
+---------------------+------------------------------------------+------------------------------------------------------+ 
| 2. Load balancing | NLB is based on IP address, port   | HLB is based only on HTTP and HTTPS     | 
|  based on  | and protocol type. Any TCP/UDP   | protocols.           | 
|      | traffic, even SMTP can be    |              | 
|      | load balanced.       |              | 
+---------------------+------------------------------------------+------------------------------------------------------+ 
|  3. Packet  | Packet inspection is possible and  | HLB cannot inspect packets.       | 
|  inspection  | load balance based on packets   |              | 
+---------------------+------------------------------------------+------------------------------------------------------+ 
|  4. Instance  | No need of creating instance group.  | Managed/UnManaged Instance group     | 
|   Group  | Target pools need to be created.   | is necessary for creating HTTP/HTTPS    | 
|      | Instance can be just tagged to the pool. | load balancer.          | 
|      | Ideal for unmanaged instance group  |              | 
|      | where instances are non homogeneous.  |              | 
+---------------------+------------------------------------------+------------------------------------------------------+ 
|  5. Workflow  | Forwarding rules is the starting point. | This is quite complex in HTTP(s) load balancer.  | 
|      | It directs the request to the   | Global forwarding rulesroutes direct the request  | 
|      | target pools from which compute   | to target HTTP proxy, which in turn checks the  | 
|      | engines will pick the request.   | URL map to determine appropriate backend    | 
|      |           | services. These services in turn direct the request | 
|      | Forwarding rules -> target pool   | to the instance group.        | 
|      | -> instances       |              | 
|      |           |              | 
|      |           | Global forwarding rules -> Target HTTP proxy ->  | 
|      |           | URL map -> Backend Sevices -> instance group   | 
+---------------------+------------------------------------------+------------------------------------------------------+ 
|  6. Types of  | Basic network load balancer which  | 1. Cross-region load balancer uses only one   | 
| load balancer | directs the request based on IP address, | global IP address and routes the request    | 
|      | port and the protocol within the region. | to the nearest region.        | 
|      |           |              | 
|      |           | 2. Content-based load balancer is based    | 
|      |           | on the URL path. Different path rules need   | 
|      |           | different backend services. for eg: /video   | 
|      |           | and /static require two separate backend services. | 
+---------------------+------------------------------------------+------------------------------------------------------+ 
| 7. Session affinity | Session affinity can be set, but only | 1. Client IP Affinity: This directs the same   | 
|      | during the creation of target pool.  | client ip to same backend instance by    | 
|      | Once it is set, the value    | computing hash of the IP.       | 
|      | cannot be changed.      | 2. Generated Cookie Affinity: Load balancer stores | 
|      |           | cookie in clients and directs the same client to  | 
|      |           | same instance with the help of retrieved cookie.  | 
+---------------------+------------------------------------------+------------------------------------------------------+ 
| 8. Health check | Health check is optional, but network | Health can be verified by either using HTTP   | 
|      | load balancing relies on HTTP Health  | heath check or HTTPS health check.     | 
|      | checks for determining instance health. |              | 
+---------------------+------------------------------------------+------------------------------------------------------+ 

नेटवर्क लोड संतुलन उपरोक्त तालिका मेरी परिप्रेक्ष्य पर आधारित है। अगर कुछ गलत है या अगर मुझे कुछ याद आया है, तो कृपया टिप्पणी करने में संकोच न करें और मैं इसे तालिका में जोड़ दूंगा।

यहाँ GCP में एक HTTP लोड संतुलन सेट करने के निर्देशों के लिए link है।