What would be an ideal architecture for a Web application which is interactive, having n to 1000 users connected at any given moment of time. The data will be saved in DB but there should be some part of memory buffering and queuing required to serve faster.
I have a basic architecture in my mind:
There would be a Web server handling user sessions and requests; And a services that would sit between DB and Web server.
The service would be queuing data for saving as well as maintaining it in memory for faster response.
I require some views over the service to avoid request-response bottlenecking between web server. Can a WCF service configured to handle request load. Is this model robust enough to maintain user integrity and response speed.
This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)