Hello! First of all, many thanks for your https://servicemesh.es/ web site, it's a very nice and useful reference point!
Then, I hope it's OK to start with a PR without creating an issue first, I did not find any contribution guidelines if it is OK or not. Just let me know if you prefer me to create an issue first.
Then, I propose removing the arrow between the two microservices in the "Microservices + Service Mesh" situation. In my experience, the proxies must intercept all the network traffic otherwise it would like there is no service mesh.
Would you agree? Maybe you have use cases that required splitting the network traffic between data-plane-traffic and non-data-plane-traffic at the same time? I am not familiar with such a use case, in my experience, the data plane should take control of all traffic between microservices.
Hello! First of all, many thanks for your https://servicemesh.es/ web site, it's a very nice and useful reference point!
Then, I hope it's OK to start with a PR without creating an issue first, I did not find any contribution guidelines if it is OK or not. Just let me know if you prefer me to create an issue first.
Then, I propose removing the arrow between the two microservices in the "Microservices + Service Mesh" situation. In my experience, the proxies must intercept all the network traffic otherwise it would like there is no service mesh.
Would you agree? Maybe you have use cases that required splitting the network traffic between data-plane-traffic and non-data-plane-traffic at the same time? I am not familiar with such a use case, in my experience, the data plane should take control of all traffic between microservices.