From 4b5efe7464f9d3ec8ed1ebfb641e050ebddf5648 Mon Sep 17 00:00:00 2001 From: Anubhav Mishra Date: Fri, 29 Jun 2018 17:35:58 -0700 Subject: [PATCH] website: make performance impact explicit for connect-native I was going to the public feedback on Connect-Native app integration and came across [this](https://twitter.com/relistan/status/1012263110403555329) thread. Added a few statements in the Connect-Native app integration page. --- website/source/docs/connect/native.html.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/website/source/docs/connect/native.html.md b/website/source/docs/connect/native.html.md index 1717cc3389..9986a79085 100644 --- a/website/source/docs/connect/native.html.md +++ b/website/source/docs/connect/native.html.md @@ -10,9 +10,11 @@ description: |- Applications can natively integrate with the Connect API to support accepting and establishing connections to other Connect services without -the overhead of a [proxy sidecar](/docs/connect/proxies.html). This page -will cover the high-level overview of integration, registering the service, -etc. For language-specific examples, see the sidebar navigation to the left. +the overhead of a [proxy sidecar](/docs/connect/proxies.html). This option +is especially useful for applications that may be experiencing performance issues +with the proxy sidecar deployment. This page will cover the high-level overview +of integration, registering the service, etc. For language-specific examples, +see the sidebar navigation to the left. Connect is just basic mutual TLS. This means that almost any application can easily integrate with Connect. There is no custom protocol in use;