Low latency, high load message passing and authentication using Amazon SQS or Yaws/Erlang

I would like to get software and setup help for a server "cluster" to relay messages with low latency, low bandwidth and high throughput between small groups of clients. E.g. clients play a game with 2-4 users per game room, and this involves each of them sending a message with about 20-100 bytes every 2-3 seconds to all or some of the people in the same room. I would like to get server infrastructure to and associated simple client-side library dll to broker these messages and to authenticate users, in order to be able to charge for usage. You may want to implement the message brokering server as Yaws/Erlang or using the Amazon Simple Queue Service functionality, if you can find a way to generate tokens for clients to use and then revoke them at the end of session. If you think it would be better to use something else, like ActiveBlaze or whatever, please explain. Obviously, I would like ability to support lots of concurrent users per server to save on servers, but the speed and low cost of development at this time take priority. As part of this component you will also need to make a testing server to simulate the many users accessing the message broker server. Or, just tell me some other credible way to test the ability of the system to handle a serious load. You also need to make the separate authentication server where users login and get assigned to one of the message broker servers (initially we will have one, but ideally it should scale to several later on). I would prefer authentication server to be implemented in ASP.net In your bid or comment please write some of your thoughts about the implementation, such as how do you think it would be fastest / easiest to build. Keep in mind that my budget is limited, so I am shooting for simplicity and "gets the job done" first and foremost. ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows? (depending on the nature? of the deliverables): a)? For web sites or? other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software? installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform C#, C++ , Erlang, Yaws, Asp.net, Amazon SQS