asp.net system architecture with real-time functionality

asp.net

Structure and background:

There is a system, its structure and the general B/s ratio, there is a different place, is the bottom layer (said to be a layer, in fact, is a separate program), this layer is the WinForm program, for the time being "exchange" to express it. Mainly used for "external" communication, send and receive and process some information. Specifically do not repeat.

So the structure of the system now is:

Client--web Server (presentation layer--logical layer--data access Layer)--database--exchange--External

Some "real time" communications are required (in real time, of course). In fact, it is impossible to do like CS, just in the "client" to do the timer, the "external" data sent in a timely manner to "client" or "client" sent to the "external" data. We call it "real Time communications." Most of the time "external" data is to be stored directly from the "Exchange" into the database for later use, we call it "regular communications."

There are currently two options:

Whether it is "real-time communication" or "regular communication", "Exchange" data received from the external to the database, the client regularly to find a Web server, the Web server to the database to fetch data, and then return. The client's data is also sent directly to the database and then "swapped" to read the data and forward it to "external". The figure of a line above is the specific one.

This requires a higher database, because all the data through the database, involving a large number of data exchange and table operations, do not know SQL2005 can resist the live.

For "Real-time communication", the "swap" layer is used as the remoting Server,web server as the remoting client. That is, the implementation of the Web server directly and the "Exchange" program to communicate, this time the data are stored in the "Exchange" program in the memory of the computer, the client timed or timed to find a Web server. and "Regular communications" is handled in the first way. The structure is based on the above line and a Web server directly and "switched" the branch of the communication, when needed (that is, "real-time communication" when the data are gone this branch.)

Will there be any problem with this approach? I am not familiar with the remoting, to a degree of such a structure can be a little bit of the spectrum is not.

Difference:

In both of these ways, the structure of the "Regular communications" section is fine. The key is the "Live Communications" section, which simply means whether the data is going from the database or the Web server directly and "swapping" traffic.

It is now necessary to consider what structure is required:

A certain server can not be too much pressure, otherwise the system cannot afford. ("external" has a very large amount of concurrency)

Two pairs of "Real-time communications" section of the performance requirements are very high.

Attention:

A BS structure has been set up, can not be changed. (The company's previous project is C/s, now want to transition to B/s)

There is no problem with the hardware, each piece is a separate high configuration server.

Three may be the "exchange" of this part of the understanding is not very clear, in fact, it has to be responsible for more functions, the pressure will be very large. Of course it is also a separate server.

Four configurations are basically as follows: windows2003,ms-sql2005,vs2005 and so on, are Enterprise Edition.

Problem:

One and two of the above methods of structure can be better? (mainly consider the performance of the "Real Time" section, others are not discussed)

Is there any other structure that works? or technology?

Three some things may I say is not clear, please leave a message, I will reply as soon as possible.

Do you have a friend with GPS positioning? Please leave the contact way, ask the question.