StevenACoffman · July 15, 2024 05:12 · Mar 2, 2019 · Feb 24, 2018 · Feb 24, 2018 · Feb 24, 2018
diff --git a/_MicroService Proxy Gateway Solutions.md b/_MicroService Proxy Gateway Solutions.md
@@ -3,17 +3,19 @@
 
 ### Github Star Trend:
 
-![Github Star History for Kong vs traefik vs fabio vs caddy vs Zuul](https://gist.github.com/StevenACoffman/acf1133da6c5ff5226c0f6eb8fbd8132/raw/proxy_gateway_solutions.png)
+![Github Star History for Kong vs traefik vs fabio vs caddy vs Zuul](https://gist.github.com/StevenACoffman/acf1133da6c5ff5226c0f6eb8fbd8132/raw/proxy_gateway_solutions2.png)
 
-This is just a [picture of this link](http://www.timqian.com/star-history/#Mashape/kong&containous/traefik&fabiolb/fabio&mholt/caddy&Netflix/zuul&vulcand/vulcand&linkerd/linkerd&lyft/envoy&istio/istio&TykTechnologies/tyk&heptio/contour&runconduit/conduit&datawire/ambassador) from Feb 24, 2018
+This is just a [picture of this link](https://timqian.com/star-history/#Kong/kong&containous/traefik&mholt/caddy&Netflix/zuul&linkerd/linkerd&lyft/envoy&istio/istio&heptio/contour&linkerd/linkerd2&datawire/ambassador) from March 2, 2019
+
+Originally, I had included some other solutions that have been declining in popularity, and some changed their github organization or repo. The [Feb 24, 2018 chart is here](https://gist.github.com/StevenACoffman/acf1133da6c5ff5226c0f6eb8fbd8132/raw/proxy_gateway_solutions.png) and was just a [picture of this link](http://www.timqian.com/star-history/#Mashape/kong&containous/traefik&fabiolb/fabio&mholt/caddy&Netflix/zuul&vulcand/vulcand&linkerd/linkerd&lyft/envoy&istio/istio&TykTechnologies/tyk&heptio/contour&runconduit/conduit&datawire/ambassador) from Feb 24, 2018
 
 ### Service Mesh vs Reverse Proxy
 A Service Mesh is related, but distinct from the concept of API gateways, edge proxies, and the enterprise service bus. The service mesh is a networking model that sits at a layer of abstraction above TCP/IP. A Service Mesh provides three benefits:
 + **security** (TLS for service to service authentication)
 + **intelligent** traffic management (proxy, deployed as a sidecar to the relevant service)
 + **visibility** (monitoring and tracing for troubleshooting and debugging)
 
-Lyft's Istio or Bouyant's Linkerd or Conduit are examples of a Service Mesh, while Traefik, Envoy, Kong, Zuul, etc. are API Gateway implemented using Reverse Proxy. Before Linkerd/Istio/Conduit, large companies implemented the same functionality using fat client libraries.
+Lyft's Istio or Bouyant's Linkerd or Linkerd2 are examples of a Service Mesh, while Traefik, Envoy, Kong, Zuul, etc. are API Gateway implemented using Reverse Proxy. Before Linkerd/Istio/Linkerd2, large companies implemented the same functionality using fat client libraries.
 
 > In these systems, a generalized communication layer became suddenly relevant, but typically took the form of a “fat client” library—Twitter’s Finagle, Netflix’s Hysterix, and Google’s Stubby being cases in point.
 

diff --git a/proxy_gateway_solutions2.png b/proxy_gateway_solutions2.png
diff --git a/KubernetesLoadBalancerVsIngress.png → zKubernetesLoadBalancerVsIngress.png b/KubernetesLoadBalancerVsIngress.png → zKubernetesLoadBalancerVsIngress.png
diff --git a/_MicroService Proxy Gateway Solutions.md b/_MicroService Proxy Gateway Solutions.md
@@ -1,11 +1,11 @@
 ### MicroService Proxy Gateway Solutions
-[Kong](https://github.com/Mashape/kong), [Traefik](https://github.com/containous/traefik), [Caddy](https://github.com/mholt/caddy), [Linkerd](https://github.com/linkerd/linkerd), [Fabio](https://github.com/fabiolb/fabio), [Vulcand](https://github.com/vulcand/vulcand), and [Netflix Zuul](https://github.com/Netflix/zuul) seem to be the most common in microservice proxy/gateway solutions. Kubernetes Ingress is often a simple Ngnix, which is difficult to seperate the popularity from other things.
+[Kong](https://github.com/Mashape/kong), [Traefik](https://github.com/containous/traefik), [Caddy](https://github.com/mholt/caddy), [Linkerd](https://github.com/linkerd/linkerd), [Fabio](https://github.com/fabiolb/fabio), [Vulcand](https://github.com/vulcand/vulcand), and [Netflix Zuul](https://github.com/Netflix/zuul) seem to be the most common in microservice proxy/gateway solutions. Kubernetes Ingress is often a simple Ngnix, which is difficult to separate the popularity from other things.
 
 ### Github Star Trend:
 
 ![Github Star History for Kong vs traefik vs fabio vs caddy vs Zuul](https://gist.github.com/StevenACoffman/acf1133da6c5ff5226c0f6eb8fbd8132/raw/proxy_gateway_solutions.png)
 
-This is just a [picture of this link](http://www.timqian.com/star-history/#Mashape/kong&containous/traefik&fabiolb/fabio&mholt/caddy&Netflix/zuul&vulcand/vulcand&linkerd/linkerd&lyft/envoy&istio/istio&TykTechnologies/tyk&heptio/contour&runconduit/conduit) from Feb 24, 2018
+This is just a [picture of this link](http://www.timqian.com/star-history/#Mashape/kong&containous/traefik&fabiolb/fabio&mholt/caddy&Netflix/zuul&vulcand/vulcand&linkerd/linkerd&lyft/envoy&istio/istio&TykTechnologies/tyk&heptio/contour&runconduit/conduit&datawire/ambassador) from Feb 24, 2018
 
 ### Service Mesh vs Reverse Proxy
 A Service Mesh is related, but distinct from the concept of API gateways, edge proxies, and the enterprise service bus. The service mesh is a networking model that sits at a layer of abstraction above TCP/IP. A Service Mesh provides three benefits:
@@ -17,7 +17,7 @@ Lyft's Istio or Bouyant's Linkerd or Conduit are examples of a Service Mesh, whi
 
 > In these systems, a generalized communication layer became suddenly relevant, but typically took the form of a “fat client” library—Twitter’s Finagle, Netflix’s Hysterix, and Google’s Stubby being cases in point.
 
-Some of these gateways specialize in Edge features, while others are more suitable for internal routing. 
+Some of these gateways specialize in Edge features, while others are more suitable for internal routing.
 
 More Articles:
 + [What is a Service Mesh and Why Do I Need One](https://dzone.com/articles/whats-a-service-mesh-and-why-do-i-need-one)
@@ -29,4 +29,4 @@ More Articles:
 
 
 #### Kubernetes Ingress
-It is hard to seperate the popularity of the default example NGINX kubernetes ingress controller from the rest of kubernetes. Of the alternative implementations, [this chart](http://www.timqian.com/star-history/#zalando-incubator/kube-ingress-aws-controller&coreos/alb-ingress-controller&sky-uk/feed) makes it look like [coreos/alb-ingress-controller](https://github.com/coreos/alb-ingress-controller) is the most popular for AWS.
+It is hard to seperate the popularity of the default example NGINX kubernetes ingress controller from the rest of kubernetes. Of the alternative implementations, [this chart](http://www.timqian.com/star-history/#zalando-incubator/kube-ingress-aws-controller&coreos/alb-ingress-controller&sky-uk/feed) makes it look like [coreos/alb-ingress-controller](https://github.com/coreos/alb-ingress-controller) is the most popular for AWS.
diff --git a/proxy_gateway_solutions.png b/proxy_gateway_solutions.png
diff --git a/_MicroService Proxy Gateway Solutions.md b/_MicroService Proxy Gateway Solutions.md
@@ -5,7 +5,7 @@
 
 ![Github Star History for Kong vs traefik vs fabio vs caddy vs Zuul](https://gist.github.com/StevenACoffman/acf1133da6c5ff5226c0f6eb8fbd8132/raw/proxy_gateway_solutions.png)
 
-This is just a [picture of this link](http://www.timqian.com/star-history/#Mashape/kong&containous/traefik&fabiolb/fabio&mholt/caddy&Netflix/zuul&vulcand/vulcand&linkerd/linkerd&lyft/envoy&istio/istio&TykTechnologies/tyk&heptio/contour&runconduit/conduit) from July 13, 2017
+This is just a [picture of this link](http://www.timqian.com/star-history/#Mashape/kong&containous/traefik&fabiolb/fabio&mholt/caddy&Netflix/zuul&vulcand/vulcand&linkerd/linkerd&lyft/envoy&istio/istio&TykTechnologies/tyk&heptio/contour&runconduit/conduit) from Feb 24, 2018
 
 ### Service Mesh vs Reverse Proxy
 A Service Mesh is related, but distinct from the concept of API gateways, edge proxies, and the enterprise service bus. The service mesh is a networking model that sits at a layer of abstraction above TCP/IP. A Service Mesh provides three benefits:
@@ -17,7 +17,7 @@ Lyft's Istio or Bouyant's Linkerd or Conduit are examples of a Service Mesh, whi
 
 > In these systems, a generalized communication layer became suddenly relevant, but typically took the form of a “fat client” library—Twitter’s Finagle, Netflix’s Hysterix, and Google’s Stubby being cases in point.
 
-Some of these gateways specialize in Edge, while others are more suitable for internal routing. 
+Some of these gateways specialize in Edge features, while others are more suitable for internal routing. 
 
 More Articles:
 + [What is a Service Mesh and Why Do I Need One](https://dzone.com/articles/whats-a-service-mesh-and-why-do-i-need-one)

diff --git a/proxy_gateway_solutions.png b/proxy_gateway_solutions.png
diff --git a/MicroService Proxy Gateway Solutions.md → _MicroService Proxy Gateway Solutions.md b/MicroService Proxy Gateway Solutions.md → _MicroService Proxy Gateway Solutions.md
diff --git a/MicroService Proxy Gateway Solutions.md b/MicroService Proxy Gateway Solutions.md
@@ -1,5 +1,5 @@
 ### MicroService Proxy Gateway Solutions
-[Kong](https://github.com/Mashape/kong), [Traefik](https://github.com/containous/traefik), [Caddy](https://github.com/mholt/caddy), [Linkerd](https://github.com/linkerd/linkerd), [Fabio](https://github.com/fabiolb/fabio), [Vulcand](https://github.com/vulcand/vulcand), and [Netflix Zuul](https://github.com/Netflix/zuul) seem to the most common in microservice proxy/gateway solutions. Kubernetes Ingress is often a simple Ngnix, which is difficult to seperate the popularity from other things.
+[Kong](https://github.com/Mashape/kong), [Traefik](https://github.com/containous/traefik), [Caddy](https://github.com/mholt/caddy), [Linkerd](https://github.com/linkerd/linkerd), [Fabio](https://github.com/fabiolb/fabio), [Vulcand](https://github.com/vulcand/vulcand), and [Netflix Zuul](https://github.com/Netflix/zuul) seem to be the most common in microservice proxy/gateway solutions. Kubernetes Ingress is often a simple Ngnix, which is difficult to seperate the popularity from other things.
 
 ### Github Star Trend:
 
@@ -13,10 +13,12 @@ A Service Mesh is related, but distinct from the concept of API gateways, edge p
 + **intelligent** traffic management (proxy, deployed as a sidecar to the relevant service)
 + **visibility** (monitoring and tracing for troubleshooting and debugging)
 
-Lyft's Istio or Twitter's Linkerd are examples of a Service Mesh, while Traefik, Envoy, Kong, Zuul, etc. are API Gateway implemented using Reverse Proxy. Before Linkerd/Istio, large companies implemented the same functionality using fat client libraries.
+Lyft's Istio or Bouyant's Linkerd or Conduit are examples of a Service Mesh, while Traefik, Envoy, Kong, Zuul, etc. are API Gateway implemented using Reverse Proxy. Before Linkerd/Istio/Conduit, large companies implemented the same functionality using fat client libraries.
 
 > In these systems, a generalized communication layer became suddenly relevant, but typically took the form of a “fat client” library—Twitter’s Finagle, Netflix’s Hysterix, and Google’s Stubby being cases in point.
 
+Some of these gateways specialize in Edge, while others are more suitable for internal routing. 
+
 More Articles:
 + [What is a Service Mesh and Why Do I Need One](https://dzone.com/articles/whats-a-service-mesh-and-why-do-i-need-one)
 + [So what even is a Service Mesh? Hot take on Istio and Linkerd](http://redmonk.com/jgovernor/2017/05/31/so-what-even-is-a-service-mesh-hot-take-on-istio-and-linkerd/)

diff --git a/MicroService Proxy Gateway Solutions.md b/MicroService Proxy Gateway Solutions.md
@@ -23,6 +23,7 @@ More Articles:
 + [Pivotal and Istio: Advancing the Ecosystem for Microservices in the Enterprise](https://content.pivotal.io/blog/pivotal-and-istio-advancing-the-ecosystem-for-microservices-in-the-enterprise)
 + [Linkerd and Istio: Like Peanut Butter and Jelly](https://buoyant.io/2017/07/11/linkerd-istio/)
 + [Lyft Envoy Comparison to alternatives](https://lyft.github.io/envoy/docs/intro/comparison.html#id7)
++ [Introduction to modern network load balancing and proxying](https://blog.envoyproxy.io/introduction-to-modern-network-load-balancing-and-proxying-a57f6ff80236)
 
 
 #### Kubernetes Ingress

diff --git a/MicroService Proxy Gateway Solutions.md → MicroService Proxy Gateway Solutions.md b/MicroService Proxy Gateway Solutions.md → MicroService Proxy Gateway Solutions.md
@@ -5,7 +5,7 @@
 
 ![Github Star History for Kong vs traefik vs fabio vs caddy vs Zuul](https://gist.github.com/StevenACoffman/acf1133da6c5ff5226c0f6eb8fbd8132/raw/proxy_gateway_solutions.png)
 
-This is just a [picture of this link](http://www.timqian.com/star-history/#Mashape/kong&containous/traefik&fabiolb/fabio&mholt/caddy&Netflix/zuul&vulcand/vulcand&linkerd/linkerd&lyft/envoy&istio/istio&TykTechnologies/tyk) from July 13, 2017
+This is just a [picture of this link](http://www.timqian.com/star-history/#Mashape/kong&containous/traefik&fabiolb/fabio&mholt/caddy&Netflix/zuul&vulcand/vulcand&linkerd/linkerd&lyft/envoy&istio/istio&TykTechnologies/tyk&heptio/contour&runconduit/conduit) from July 13, 2017
 
 ### Service Mesh vs Reverse Proxy
 A Service Mesh is related, but distinct from the concept of API gateways, edge proxies, and the enterprise service bus. The service mesh is a networking model that sits at a layer of abstraction above TCP/IP. A Service Mesh provides three benefits:

diff --git a/MicroService Proxy Gateway Solutions.md b/MicroService Proxy Gateway Solutions.md
@@ -5,7 +5,7 @@
 
 ![Github Star History for Kong vs traefik vs fabio vs caddy vs Zuul](https://gist.github.com/StevenACoffman/acf1133da6c5ff5226c0f6eb8fbd8132/raw/proxy_gateway_solutions.png)
 
-This is just a [picture of this link](http://www.timqian.com/star-history/#Mashape/kong&containous/traefik&fabiolb/fabio&mholt/caddy&Netflix/zuul&vulcand/vulcand&linkerd/linkerd&lyft/envoy&istio/istio) from July 13, 2017
+This is just a [picture of this link](http://www.timqian.com/star-history/#Mashape/kong&containous/traefik&fabiolb/fabio&mholt/caddy&Netflix/zuul&vulcand/vulcand&linkerd/linkerd&lyft/envoy&istio/istio&TykTechnologies/tyk) from July 13, 2017
 
 ### Service Mesh vs Reverse Proxy
 A Service Mesh is related, but distinct from the concept of API gateways, edge proxies, and the enterprise service bus. The service mesh is a networking model that sits at a layer of abstraction above TCP/IP. A Service Mesh provides three benefits:

diff --git a/KubernetesLoadBalancerVsIngress.png b/KubernetesLoadBalancerVsIngress.png
diff --git a/MicroService Proxy Gateway Solutions.md b/MicroService Proxy Gateway Solutions.md
@@ -22,4 +22,8 @@ More Articles:
 + [So what even is a Service Mesh? Hot take on Istio and Linkerd](http://redmonk.com/jgovernor/2017/05/31/so-what-even-is-a-service-mesh-hot-take-on-istio-and-linkerd/)
 + [Pivotal and Istio: Advancing the Ecosystem for Microservices in the Enterprise](https://content.pivotal.io/blog/pivotal-and-istio-advancing-the-ecosystem-for-microservices-in-the-enterprise)
 + [Linkerd and Istio: Like Peanut Butter and Jelly](https://buoyant.io/2017/07/11/linkerd-istio/)
-+ [Lyft Envoy Comparison to alternatives](https://lyft.github.io/envoy/docs/intro/comparison.html#id7)
++ [Lyft Envoy Comparison to alternatives](https://lyft.github.io/envoy/docs/intro/comparison.html#id7)
+
+
+#### Kubernetes Ingress
+It is hard to seperate the popularity of the default example NGINX kubernetes ingress controller from the rest of kubernetes. Of the alternative implementations, [this chart](http://www.timqian.com/star-history/#zalando-incubator/kube-ingress-aws-controller&coreos/alb-ingress-controller&sky-uk/feed) makes it look like [coreos/alb-ingress-controller](https://github.com/coreos/alb-ingress-controller) is the most popular for AWS.
diff --git a/MicroService Proxy Gateway Solutions.md b/MicroService Proxy Gateway Solutions.md
@@ -22,4 +22,4 @@ More Articles:
 + [So what even is a Service Mesh? Hot take on Istio and Linkerd](http://redmonk.com/jgovernor/2017/05/31/so-what-even-is-a-service-mesh-hot-take-on-istio-and-linkerd/)
 + [Pivotal and Istio: Advancing the Ecosystem for Microservices in the Enterprise](https://content.pivotal.io/blog/pivotal-and-istio-advancing-the-ecosystem-for-microservices-in-the-enterprise)
 + [Linkerd and Istio: Like Peanut Butter and Jelly](https://buoyant.io/2017/07/11/linkerd-istio/)
-+[Lyft Envoy Comparison to alternatives](https://lyft.github.io/envoy/docs/intro/comparison.html#id7)
++ [Lyft Envoy Comparison to alternatives](https://lyft.github.io/envoy/docs/intro/comparison.html#id7)
diff --git a/MicroService Proxy Gateway Solutions.md b/MicroService Proxy Gateway Solutions.md
@@ -21,4 +21,5 @@ More Articles:
 + [What is a Service Mesh and Why Do I Need One](https://dzone.com/articles/whats-a-service-mesh-and-why-do-i-need-one)
 + [So what even is a Service Mesh? Hot take on Istio and Linkerd](http://redmonk.com/jgovernor/2017/05/31/so-what-even-is-a-service-mesh-hot-take-on-istio-and-linkerd/)
 + [Pivotal and Istio: Advancing the Ecosystem for Microservices in the Enterprise](https://content.pivotal.io/blog/pivotal-and-istio-advancing-the-ecosystem-for-microservices-in-the-enterprise)
-+ [Linkerd and Istio: Like Peanut Butter and Jelly](https://buoyant.io/2017/07/11/linkerd-istio/)
++ [Linkerd and Istio: Like Peanut Butter and Jelly](https://buoyant.io/2017/07/11/linkerd-istio/)
++[Lyft Envoy Comparison to alternatives](https://lyft.github.io/envoy/docs/intro/comparison.html#id7)
diff --git a/MicroService Proxy Gateway Solutions.md b/MicroService Proxy Gateway Solutions.md
@@ -5,7 +5,7 @@
 
 ![Github Star History for Kong vs traefik vs fabio vs caddy vs Zuul](https://gist.github.com/StevenACoffman/acf1133da6c5ff5226c0f6eb8fbd8132/raw/proxy_gateway_solutions.png)
 
-This is just a [picture of this link](http://www.timqian.com/star-history/#Mashape/kong&containous/traefik&fabiolb/fabio&mholt/caddy&Netflix/zuul&vulcand/vulcand&linkerd/linkerd&lyft/envoy&istio/istio) from June 28, 2017
+This is just a [picture of this link](http://www.timqian.com/star-history/#Mashape/kong&containous/traefik&fabiolb/fabio&mholt/caddy&Netflix/zuul&vulcand/vulcand&linkerd/linkerd&lyft/envoy&istio/istio) from July 13, 2017
 
 ### Service Mesh vs Reverse Proxy
 A Service Mesh is related, but distinct from the concept of API gateways, edge proxies, and the enterprise service bus. The service mesh is a networking model that sits at a layer of abstraction above TCP/IP. A Service Mesh provides three benefits:

diff --git a/proxy_gateway_solutions.png b/proxy_gateway_solutions.png
diff --git a/MicroService Proxy Gateway Solutions.md b/MicroService Proxy Gateway Solutions.md
@@ -13,7 +13,7 @@ A Service Mesh is related, but distinct from the concept of API gateways, edge p
 + **intelligent** traffic management (proxy, deployed as a sidecar to the relevant service)
 + **visibility** (monitoring and tracing for troubleshooting and debugging)
 
-Istio or Linkerd are examples of a Service Mesh, while Traefik, Envoy, Kong, Zuul, etc. are API Gateway implemented using Reverse Proxy. Before Linkerd/Istio, large companies implemented the same functionality using fat client libraries.
+Lyft's Istio or Twitter's Linkerd are examples of a Service Mesh, while Traefik, Envoy, Kong, Zuul, etc. are API Gateway implemented using Reverse Proxy. Before Linkerd/Istio, large companies implemented the same functionality using fat client libraries.
 
 > In these systems, a generalized communication layer became suddenly relevant, but typically took the form of a “fat client” library—Twitter’s Finagle, Netflix’s Hysterix, and Google’s Stubby being cases in point.
 

diff --git a/MicroService Proxy Gateway Solutions.md b/MicroService Proxy Gateway Solutions.md
@@ -9,9 +9,9 @@ This is just a [picture of this link](http://www.timqian.com/star-history/#Masha
 
 ### Service Mesh vs Reverse Proxy
 A Service Mesh is related, but distinct from the concept of API gateways, edge proxies, and the enterprise service bus. The service mesh is a networking model that sits at a layer of abstraction above TCP/IP. A Service Mesh provides three benefits:
-+ security (TLS for service to service authentication)
-+ intelligent traffic management (proxy, deployed as a sidecar to the relevant service)
-+ visibility (monitoring and tracing for troubleshooting and debugging)
++ **security** (TLS for service to service authentication)
++ **intelligent** traffic management (proxy, deployed as a sidecar to the relevant service)
++ **visibility** (monitoring and tracing for troubleshooting and debugging)
 
 Istio or Linkerd are examples of a Service Mesh, while Traefik, Envoy, Kong, Zuul, etc. are API Gateway implemented using Reverse Proxy. Before Linkerd/Istio, large companies implemented the same functionality using fat client libraries.
 

diff --git a/MicroService Proxy Gateway Solutions.md b/MicroService Proxy Gateway Solutions.md
@@ -17,7 +17,8 @@ Istio or Linkerd are examples of a Service Mesh, while Traefik, Envoy, Kong, Zuu
 
 > In these systems, a generalized communication layer became suddenly relevant, but typically took the form of a “fat client” library—Twitter’s Finagle, Netflix’s Hysterix, and Google’s Stubby being cases in point.
 
-[What is a Service Mesh and Why Do I Need One](https://dzone.com/articles/whats-a-service-mesh-and-why-do-i-need-one)
-[So what even is a Service Mesh? Hot take on Istio and Linkerd](http://redmonk.com/jgovernor/2017/05/31/so-what-even-is-a-service-mesh-hot-take-on-istio-and-linkerd/)
-[Pivotal and Istio: Advancing the Ecosystem for Microservices in the Enterprise](https://content.pivotal.io/blog/pivotal-and-istio-advancing-the-ecosystem-for-microservices-in-the-enterprise)
-[Linkerd and Istio: Like Peanut Butter and Jelly](https://buoyant.io/2017/07/11/linkerd-istio/)
+More Articles:
++ [What is a Service Mesh and Why Do I Need One](https://dzone.com/articles/whats-a-service-mesh-and-why-do-i-need-one)
++ [So what even is a Service Mesh? Hot take on Istio and Linkerd](http://redmonk.com/jgovernor/2017/05/31/so-what-even-is-a-service-mesh-hot-take-on-istio-and-linkerd/)
++ [Pivotal and Istio: Advancing the Ecosystem for Microservices in the Enterprise](https://content.pivotal.io/blog/pivotal-and-istio-advancing-the-ecosystem-for-microservices-in-the-enterprise)
++ [Linkerd and Istio: Like Peanut Butter and Jelly](https://buoyant.io/2017/07/11/linkerd-istio/)
diff --git a/MicroService Proxy Gateway Solutions.md b/MicroService Proxy Gateway Solutions.md
@@ -1,8 +1,23 @@
 ### MicroService Proxy Gateway Solutions
-[Kong](https://github.com/Mashape/kong), [Traefik](https://github.com/containous/traefik), [Caddy](https://github.com/mholt/caddy), [Linkerd](https://github.com/linkerd/linkerd), [Fabio](https://github.com/fabiolb/fabio), [Vulcand](https://github.com/vulcand/vulcand), and [Netflix Zuul](https://github.com/Netflix/zuul) seem to the most common in microservice proxy/gateway solutions.
+[Kong](https://github.com/Mashape/kong), [Traefik](https://github.com/containous/traefik), [Caddy](https://github.com/mholt/caddy), [Linkerd](https://github.com/linkerd/linkerd), [Fabio](https://github.com/fabiolb/fabio), [Vulcand](https://github.com/vulcand/vulcand), and [Netflix Zuul](https://github.com/Netflix/zuul) seem to the most common in microservice proxy/gateway solutions. Kubernetes Ingress is often a simple Ngnix, which is difficult to seperate the popularity from other things.
 
 ### Github Star Trend:
 
 ![Github Star History for Kong vs traefik vs fabio vs caddy vs Zuul](https://gist.github.com/StevenACoffman/acf1133da6c5ff5226c0f6eb8fbd8132/raw/proxy_gateway_solutions.png)
 
-This is just a [picture of this link](http://www.timqian.com/star-history/#Mashape/kong&containous/traefik&fabiolb/fabio&mholt/caddy&Netflix/zuul&vulcand/vulcand&linkerd/linkerd&lyft/envoy&istio/istio) from June 28, 2017
+This is just a [picture of this link](http://www.timqian.com/star-history/#Mashape/kong&containous/traefik&fabiolb/fabio&mholt/caddy&Netflix/zuul&vulcand/vulcand&linkerd/linkerd&lyft/envoy&istio/istio) from June 28, 2017
+
+### Service Mesh vs Reverse Proxy
+A Service Mesh is related, but distinct from the concept of API gateways, edge proxies, and the enterprise service bus. The service mesh is a networking model that sits at a layer of abstraction above TCP/IP. A Service Mesh provides three benefits:
++ security (TLS for service to service authentication)
++ intelligent traffic management (proxy, deployed as a sidecar to the relevant service)
++ visibility (monitoring and tracing for troubleshooting and debugging)
+
+Istio or Linkerd are examples of a Service Mesh, while Traefik, Envoy, Kong, Zuul, etc. are API Gateway implemented using Reverse Proxy. Before Linkerd/Istio, large companies implemented the same functionality using fat client libraries.
+
+> In these systems, a generalized communication layer became suddenly relevant, but typically took the form of a “fat client” library—Twitter’s Finagle, Netflix’s Hysterix, and Google’s Stubby being cases in point.
+
+[What is a Service Mesh and Why Do I Need One](https://dzone.com/articles/whats-a-service-mesh-and-why-do-i-need-one)
+[So what even is a Service Mesh? Hot take on Istio and Linkerd](http://redmonk.com/jgovernor/2017/05/31/so-what-even-is-a-service-mesh-hot-take-on-istio-and-linkerd/)
+[Pivotal and Istio: Advancing the Ecosystem for Microservices in the Enterprise](https://content.pivotal.io/blog/pivotal-and-istio-advancing-the-ecosystem-for-microservices-in-the-enterprise)
+[Linkerd and Istio: Like Peanut Butter and Jelly](https://buoyant.io/2017/07/11/linkerd-istio/)
diff --git a/MicroService Proxy Gateway Solutions.md b/MicroService Proxy Gateway Solutions.md
@@ -5,4 +5,4 @@
 
 ![Github Star History for Kong vs traefik vs fabio vs caddy vs Zuul](https://gist.github.com/StevenACoffman/acf1133da6c5ff5226c0f6eb8fbd8132/raw/proxy_gateway_solutions.png)
 
-This is just a [picture of this link](http://www.timqian.com/star-history/#Mashape/kong&containous/traefik&fabiolb/fabio&mholt/caddy&Netflix/zuul&vulcand/vulcand&linkerd/linkerd) from June 28, 2017
+This is just a [picture of this link](http://www.timqian.com/star-history/#Mashape/kong&containous/traefik&fabiolb/fabio&mholt/caddy&Netflix/zuul&vulcand/vulcand&linkerd/linkerd&lyft/envoy&istio/istio) from June 28, 2017
diff --git a/MicroService Proxy Gateway Solutions.md b/MicroService Proxy Gateway Solutions.md
@@ -1,5 +1,5 @@
 ### MicroService Proxy Gateway Solutions
-[Linkerd](https://github.com/linkerd/linkerd), [Vulcand](https://github.com/vulcand/vulcand), [Kong](https://github.com/Mashape/kong), [Traefik](https://github.com/containous/traefik), [Fabio](https://github.com/fabiolb/fabio), [Caddy](https://github.com/mholt/caddy), and [Netflix Zuul](https://github.com/Netflix/zuul) seem to the most common in microservice proxy/gateway solutions.
+[Kong](https://github.com/Mashape/kong), [Traefik](https://github.com/containous/traefik), [Caddy](https://github.com/mholt/caddy), [Linkerd](https://github.com/linkerd/linkerd), [Fabio](https://github.com/fabiolb/fabio), [Vulcand](https://github.com/vulcand/vulcand), and [Netflix Zuul](https://github.com/Netflix/zuul) seem to the most common in microservice proxy/gateway solutions.
 
 ### Github Star Trend:
 

diff --git a/MicroService Proxy Gateway Solutions.md b/MicroService Proxy Gateway Solutions.md
@@ -1,5 +1,5 @@
 ### MicroService Proxy Gateway Solutions
-[Kong](https://github.com/Mashape/kong), [Traefik](https://github.com/containous/traefik), [Fabio](https://github.com/fabiolb/fabio), [Caddy](https://github.com/mholt/caddy), and [Netflix Zuul](https://github.com/Netflix/zuul) seem to the most common in microservice proxy/gateway solutions.
+[Linkerd](https://github.com/linkerd/linkerd), [Vulcand](https://github.com/vulcand/vulcand), [Kong](https://github.com/Mashape/kong), [Traefik](https://github.com/containous/traefik), [Fabio](https://github.com/fabiolb/fabio), [Caddy](https://github.com/mholt/caddy), and [Netflix Zuul](https://github.com/Netflix/zuul) seem to the most common in microservice proxy/gateway solutions.
 
 ### Github Star Trend:
 

diff --git a/MicroService Proxy Gateway Solutions.md b/MicroService Proxy Gateway Solutions.md
@@ -5,4 +5,4 @@
 
 ![Github Star History for Kong vs traefik vs fabio vs caddy vs Zuul](https://gist.github.com/StevenACoffman/acf1133da6c5ff5226c0f6eb8fbd8132/raw/proxy_gateway_solutions.png)
 
-This is just a [picture of this link](http://www.timqian.com/star-history/#Mashape/kong&containous/traefik&fabiolb/fabio&mholt/caddy&Netflix/zuul) from June 26, 2017
+This is just a [picture of this link](http://www.timqian.com/star-history/#Mashape/kong&containous/traefik&fabiolb/fabio&mholt/caddy&Netflix/zuul&vulcand/vulcand&linkerd/linkerd) from June 28, 2017
diff --git a/proxy_gateway_solutions.png b/proxy_gateway_solutions.png
diff --git a/MicroService Proxy Gateway Solutions.md b/MicroService Proxy Gateway Solutions.md
@@ -1,5 +1,5 @@
 ### MicroService Proxy Gateway Solutions
-Traefik , Fabio, Kong, Caddy, Zuul seem to the most common in microservice proxy/gateway solutions
+[Kong](https://github.com/Mashape/kong), [Traefik](https://github.com/containous/traefik), [Fabio](https://github.com/fabiolb/fabio), [Caddy](https://github.com/mholt/caddy), and [Netflix Zuul](https://github.com/Netflix/zuul) seem to the most common in microservice proxy/gateway solutions.
 
 ### Github Star Trend:
 

diff --git a/proxy_gateway_solutions.png b/proxy_gateway_solutions.png
diff --git a/MicroService Proxy Gateway Solutions.md b/MicroService Proxy Gateway Solutions.md
@@ -1 +1,8 @@
-traefik , fabio, kong , caddy seem to the most common in microservice proxy/gateway solutions
+### MicroService Proxy Gateway Solutions
+Traefik , Fabio, Kong, Caddy, Zuul seem to the most common in microservice proxy/gateway solutions
+
+### Github Star Trend:
+
+![Github Star History for Kong vs traefik vs fabio vs caddy vs Zuul](https://gist.github.com/StevenACoffman/acf1133da6c5ff5226c0f6eb8fbd8132/raw/proxy_gateway_solutions.png)
+
+This is just a [picture of this link](http://www.timqian.com/star-history/#Mashape/kong&containous/traefik&fabiolb/fabio&mholt/caddy&Netflix/zuul) from June 26, 2017