Browse files

Clarify kage is EM-based and shadow traffic is handled asynchronously…

… without blocking clients.
  • Loading branch information...
miyagawa committed Oct 30, 2012
1 parent 2faa68c commit d5a342e2802e93225f63b55a94065bb8ddbf2c84
Showing with 2 additions and 0 deletions.
  1. +2 −0
@@ -4,6 +4,8 @@ Kage (kah-geh) is an HTTP shadow proxy server that sits between clients and your
Kage can be used to duplex requests to the master (production) server and shadow servers that have newer code changes that are going to be deployed. By shadowing requests to the new code you can make sure there are no big/surprising changes in the response in terms of data, performance and database loads etc.
+Kage is built with EventMachine and em-proxy and all shadow requests are done asynchronously, while responses from master are sent back to the client without blocking the network, so clients will never notice any delays even when shadow traffic is made.
You can customize the behavior of Kage with simple callbacks, when it chooses which backends to send shadow requests to (or not at all), appends or deletes HTTP headers per backend, and examines the complete HTTP response (including headers and body).
## Features

0 comments on commit d5a342e

Please sign in to comment.