S
S
Sergey Mushtuk2014-01-21 16:05:57
SQL
Sergey Mushtuk, 2014-01-21 16:05:57

Can the site access the 1C database directly or is it better for the site to work with its database and synchronize it with the 1C database?

There is 1C with a database of clients and information on them.
There is a site on which this information needs to be displayed - both on the pages of the site and on request through a web form. It is also supposed to change information about clients through the web form - their data, status, etc.
The question is, can the site access the 1C database directly or is it better for the site to work with its database and synchronize it with the 1C database?
1C version 8, so the tables are not static and accessing them directly looks like a difficult task.
It requires high speed, tens of thousands of clients (records in the database), thousands of transactions per day, hundreds of managers working with a web form and sending requests to change data.
PS
I read
habrahabr.ru/post/139272 - sorry, copying every knock
Integration of the site with the database 1C: Enterprise 8
habrahabr.ru/post/137888
infostart.ru/public/90666 - sorry, only reading

Answer the question

In order to leave comments, you need to log in

2 answer(s)
S
sharpshooter, 2014-01-21
@Osaka

Look at 1C web services, now there are http services

A
Alexander Kind, 2014-01-21
@shineblu

Good afternoon,
As an option, I can offer the following scheme
1. An intermediate server is raised with a DBMS (for example, MySQL)
2. Processing is written for 1C, which at certain intervals (once a day or every hour) will upload customer data, their statuses and etc. At the same time, after uploading to the MySQL database, a flag is set in the 1C client card - uploaded. With any movements in 1C, this flag must be reset (so as not to unload the entire database each time). Those. after a full unload, only changes will be unloaded. Also, this processing makes a SELECT from the MySQL database of those records that also have the "To unload" flag in order to change the internal data in 1C.
3. Your application will only communicate with the MySQL database - it will be an order of magnitude faster and safer + you can do caching + you can do something like an API (to make it even safer)
Good luck!

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question