Hi - I've been pulling my hair out for the last month trying to make the right choice for our systems middle tier. I was hoping that someone out there might be able to suggest the best fit: basically we are building an IVR system with C#.NET, handling potentially 100's of calls on competition lines every minute. Different info is retrieved for each call and stored in SQLServer (but we would like to have database independance). Up to 10's of thousands of operators will be stored in the database (basic info: name, number, address, PIN). Callers are routed to the correct operator. We will probably be running a clustered server, all on local network (we will provide internet functionality further down the line but not immediate concern). GUI displays in realtime how many callers are phoning on which competition line (a grid of ports) and how long each has been on the phone. GUI will also allow batch entry/change to operator info. We currently use basic sockets but would remoting, message queueing or EnterpriseServices be better now that we are scaling up? We would like to achieve some degree of platform independance and handle (theoretically) limitless volumes of calls and operator info. I've been looking at asynchronous remoting but we need to use events and I am concerned about the performance hit in using message qeueuing or EnterpriseServices given the realtime nature of the system as opposed to the extra benefits each of these architectures can bring. I know this is a cheeky question but we are a small company and really can't afford to get in an architect. Any info would be greatly appreciated.
=================================== This list is hosted by DevelopMentorŪ http://www.develop.com NEW! ASP.NET courses you may be interested in: 2 Days of ASP.NET, 29 Sept 2003, in Redmond http://www.develop.com/courses/2daspdotnet Guerrilla ASP.NET, 13 Oct 2003, in Boston http://www.develop.com/courses/gaspdotnet View archives and manage your subscription(s) at http://discuss.develop.com
