HTTP/JSON을 gRPC로 트랜스코딩 하기 위한 envoy proxy sample 입니다.
client로 부터 전달 받은 request를 Api gateway에서 Envoy proxy로 전달하면 Envoy에서 gRPC로 트랜스코딩 후 gRPC Server로 전달된다.
$ ./compile-proto.sh
$ ./build-gateway.sh
$ docker-compose up -d
$ curl -XGET http://localhost:8000/helloworld?name=test
├── api
├── envoy-config
├── gateway
└── idl
- api: mali.js로 grpc server를 실행시킵니다.
- envoy-config: envoy관련 설정은 해당 디렉토리에 envoy.yml에 정의 합니다.
- gateway: spring cloud gateway로 api gateway를 실행시킵니다.
- idl: *.proto을 관리합니다.
L7 proxy and communication bus designed for large modern service oriented architectures.
Envoy is a self contained process that is designed to run alongside every application server. All of the Envoys form a transparent communication mesh in which each application sends and receives messages to and from localhost and is unaware of the network topology. The out of process architecture has two substantial benefits over the traditional library approach to service to service communication:
-
Envoy works with any application language. A single Envoy deployment can form a mesh between Java, C++, Go, PHP, Python, etc. It is becoming increasingly common for service oriented architectures to use multiple application frameworks and languages. Envoy transparently bridges the gap.
-
As anyone that has worked with a large service oriented architecture knows, deploying library upgrades can be incredibly painful. Envoy can be deployed and upgraded quickly across an entire infrastructure transparently.
gRPC is an RPC framework from Google that uses HTTP/2 as the underlying multiplexed transport. Envoy supports all of the HTTP/2 features required to be used as the routing and load balancing substrate for gRPC requests and responses. The two systems are very complementary.