<div class="gmail_quote">On Wed, Mar 31, 2010 at 4:37 AM, Ryan Malayter <span dir="ltr"><<a href="mailto:malayter@gmail.com">malayter@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5">On Mon, Mar 29, 2010 at 4:28 PM, matthieu Labour<br>
<<a href="mailto:matthieu.labour@gmail.com">matthieu.labour@gmail.com</a>> wrote:<br>
> Hi<br>
><br>
> I am new to nginx.<br>
><br>
> Can i use nginx to repeat / duplicate incoming requests ...? I understand<br>
> that I can use nginx to load balance ... but in my use case, i need to<br>
> duplicate the request. The incoming request should be routed to server0 AND<br>
> server1. Is it possible with nginx? Thank you for your help<br>
> matt<br>
<br>
</div></div>Assuming such a thing were possible, what could you sensibly do with<br>
two responses to the same request? Send only the first one to the<br>
client? Compare if they are different and send an error if they are?<br>
<br>
Or do you want to send only POSTS to multiple back-end systems to keep<br>
them in sync somehow (not a reliable mechanism, as you will miss loads<br>
of requests when a back-end is down)?<br>
<font color="#888888"><br></font></blockquote><div><br></div><div>I tought as well the idea was pretty unusual, as it's twice the work and you usually want to do as less as possible!</div><div>Anyway, depending on load, expected availability, if it' a proof of concept or something like that, I'd work on a minimal, self rolled "duplexing proxy"... a minimal version should be < 100 lines of ruby or similar languages....but it really depends a lot on what's needed.</div>
<div>If the idea was instead just that of benchmarking two different versions of some service, I'd rather record the requested urls and then play them back to different backends.</div><div><br></div><div>Bye</div><div>
<br></div></div>