Is it justified to use SOAP in 1C to organize a session key for users of an online store?

I

ItWheel2017-11-20 23:09:07

SQL

ItWheel, 2017-11-20 23:09:07

There is a self-written 1C database in conjunction with MS SQL 2014 (not express, a license for 4 cores), which implements a mechanism for storing user data (personal data, e-mail and passwords), as well as data on user orders and statuses of these orders + files of shipping documents, contracts. A self-written CMS is planned on a remote linux server, a VPN channel is planned between CMS and 1C, this channel should be used for one-way replication from MS SQL to a certain CMS database in real time by commodity items and folders with photos, i.e. the remote server will store only the products, their description, availability, prices and photos.
When a user is authorized on the site in his personal account, the CMS accesses the 1C database via SOAP, and if the password and login are correct (1C generates a session key for N hours), data from 1C on orders is loaded via SOAP (on the page no more than 9 orders), when switching to pages, data is loaded on orders located in earlier periods.
How justified is the use of SOAP for such authorization and loading of personal data from the database?
Maybe there are better solutions?
I repeat, the task is not to place personal data on a remote web server, but to organize work with them through a remote web server.

Reply

Answer the question

In order to leave comments, you need to log in

3 answer(s)

K

Konstantin Nagibovich, 2017-11-21
@nki

SOAP is only a protocol and its use is the choice of the developer. There are other mechanisms for the interaction of 1C and third-party systems. Choose the one that is more familiar/comfortable to you. In this case, I don't see anything wrong with you.

K

Konstantin, 2017-11-21
@fosihas

And this option: www.oknosoft.ru/metadata

N

nuctoh, 2018-01-17
@nuctoh

SOAP is the slowest way to exchange a site with 1C. Previously, in the days of 8.1, you had to use 1C Web Services, because. stupidly there were no other mechanisms. Now there is an HTTP Service that works faster both on the 1C server side and on the web server side, because soap client initialization is not a fast procedure even with wsdl caching.