Skip to content

gevg/envoy-play

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

5 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Envoy Play

Envoy looks plenty useful, but its reference configurations are designed for a scale I don't have to deal with yet. A single layer of proxies should be able to proxy both customer requests and internal requests.

Usage

  • docker-compose up in one terminal
  • curl -D - http://0.0.0.0:8080/first in another

You should see curl output resembling:

HTTP/1.1 200 OK
date: Sun, 01 Oct 2017 05:57:44 GMT
content-length: 13
content-type: text/plain; charset=utf-8
x-envoy-upstream-service-time: 12
server: envoy

first
second

Composition

We're running four containers:

  • The first service, which needs to talk to the second before replying
  • The second service,
  • The envoy service, and
  • The discovery service answering Envoy's /v1/clusters and /v1/registration requests

To demonstrate both customer-service and service-service proxying, we've set up first to talk to second via envoy.

Resources:

About

I'm playing with the Envoy Proxy

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Go 100.0%