Now I am thinking about the implementation of the connection between the site and 1C in real-time mode. Base 1C in MSSQL.
While I see only one main option is integration via SOAP, when adding or changing data in 1C, send a SOAP request to the site. And also from the site, send a request when changing any data.
Someone offers to work directly with the database, without describing the services.
I would like to find a more productive solution, so that the speed of the site would not greatly affect the communication in 1C.
I will be glad to see some useful links, or examples.
2 answers
Other people's examples here can play a disservice. the challenge is serious.
If you can not find the answer - "look at the requirements."
What I mean? - ask yourself questions:
What do you want to display on the site?
What is your understanding of real-time?
- How quickly should a website user change information?
For example, a user came to the site, sticks into a report, at this moment the data in the database changed - how should the site behave? will the user see updates only after refreshing the page? or right away?
Depending on the answers to these questions, some solution will emerge.
- I think these moments are not so important, because In any case, the data will be sent to the server, and how to display them is a separate question and, in general, it has nothing to do with 1C. At least we will update them immediately via AJAX, or after updating the page it is a formality. The most important thing for me is to understand a more productive process in terms of real-time 1C <-> Website - Vayas
- Are you sure that the site needs its own personal database? maybe he could use 1C directly? - Stranger in the Q
- 100% Website needs its own personal database - Vayas
- and what will be in it? - Stranger in the Q
- onejust since you are synchronizing between the bases, you bury your "rake in the garden" if you are figuratively speaking - Stranger in the Q
I already gave links How to call a method from C # in 1?
You can select the standard options. HTTP and Web services and ODATA. Non-standard is direct access through Linq to EF, use of SignalR and other web sockets.
The links are the majority. For HTTP services for example here
https://its.1c.ru/db/metod8dev#contentve756:hdoc:_top:http%20%D1%81%D0%B5%D1%80%D0BB2%D0%B8%D1