For better understanding we will use the following naming convention:
[ L1 ][ L2 ][ L3 ][ Space ][ R1 ][ R2 ][ R3 ]
| package main | |
| import ( | |
| "flag" | |
| "log" | |
| "os" | |
| "syscall" | |
| "unsafe" | |
| "path/filepath" | |
| "bufio" |
Just documenting docs, articles, and discussion related to gRPC and load balancing.
https://github.com/grpc/grpc/blob/master/doc/load-balancing.md
Seems gRPC prefers thin client-side load balancing where a client gets a list of connected clients and a load balancing policy from a "load balancer" and then performs client-side load balancing based on the information. However, this could be useful for traditional load banaling approaches in clound deployments.
https://groups.google.com/forum/#!topic/grpc-io/8s7UHY_Q1po
gRPC "works" in AWS. That is, you can run gRPC services on EC2 nodes and have them connect to other nodes, and everything is fine. If you are using AWS for easy access to hardware then all is fine. What doesn't work is ELB (aka CLB), and ALBs. Neither of these support HTTP/2 (h2c) in a way that gRPC needs.
| { | |
| "window.zoomLevel": 0, | |
| "go.lintOnSave": "package", | |
| "editor.fontFamily": "'Fira Code', Menlo, Monaco, 'Courier New', monospace", | |
| "editor.fontLigatures": false, | |
| "workbench.iconTheme": "vs-seti", | |
| "go.addTags": { | |
| "tags": "json", | |
| "options": "json=omitempty", | |
| "promptForTags": true, |