Sajan Jaiswal sajanjswl

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.

Introduction

This is a Hashicorp Terraform module that provisions an AWS EC2 instance for the purpose of running a given docker-compose.yml file.

Usage

# ===== OUR MAGIC DOCKER-COMPOSE.YML FILE HERE =====
# It is also possible to get Terraform to read an external `docker-compose.yml`
# file and load it into this variable.
# We'll be showing off a demo nginx page.

	version: '3'

	volumes:
	minioDB:

	services:
	minio:
	image: minio/minio
	container_name: minio
	environment:

	version: '3'

	volumes:
	mysqlDB:

	networks:
	mysql-network:
	driver: bridge

	services:

	syntax = "proto3";

	package v1;


	service FileService {
	//simple RPC
	rpc RegisterUser( RegisterUserRequest) returns (RegisterUserResponse){};

	// client-side straming RPC

	version: '3.1'


	volumes:
	mongoData:

	networks:
	mongo_net:
	driver: bridge