The conditions of the problem are, there is a client, there is an operator. Before them is a terminal on which a certain form (for example, a loan application form). At any change of any fields on this form, these changes are displayed on the screen of the operator. There can be any number of clients and operators. At the moment, I have made a WCF service, to which both the client and the operator are connected, if the data has come, it is placed in the database, or on request it is retrieved from there on demand, but this greatly loads the channel. The question is how to organize the architecture of the program? Are there technologies to solve the problem directly? Ie for example, Google Dox provides simultaneous access to the file, while not making constant requests.
1 answer
I would recommend WPF (MVVM) <-> WCF <-> Entity <-> SQL
At the same time, I believe that synchronization is better and faster to execute by means of WCF itself, leaving SQL only the function of storing intermediate and final data.
PS Unfortunately, I did not immediately notice the tags "Web" and "http". If the decision to use the web client is final and irreversible, then I recommend the ASP.Net MVC <-> WCF <-> Entity <-> SQL combination. However, the data will have to be updated via AJAX or similar methods, which will lead to regular access to the service. However, if WCF is properly configured and asynchronous methods are used, it will be necessary to really try to overload it. It is unlikely that a loan agreement will simultaneously fill in thousands of clients of the same credit institution.