Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request shadowing already present. #34

Merged
merged 3 commits into from
Aug 23, 2016
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/intro/what_is_envoy.rst
Original file line number Diff line number Diff line change
Expand Up @@ -85,9 +85,9 @@ components in a distributed system is a complex problem. Because Envoy is a self
instead of a library, it is able to implement advanced load balancing techniques in a single place
and have them be accessible to any application. Currently Envoy includes support for :ref:`automatic
retries <arch_overview_http_routing_retry>`, :ref:`circuit breaking <arch_overview_circuit_break>`,
and :ref:`global rate limiting <arch_overview_rate_limit>` via an external rate limiting service.
Future support is planned for automatic bad host outlier ejection, request racing, and request
shadowing.
:ref:`global rate limiting <arch_overview_rate_limit>` via an external rate limiting service, and
request shadowing. Future support is planned for automatic bad host outlier ejection and request
racing.

**Front/edge proxy support:** Although Envoy is primarily designed as a service to service
communication system, there is benefit in using the same software at the edge (observability,
Expand Down