Integrations
for data exchange between IT systems

The problem

Solution

The problem

Different systems need the same data. Consumers duplicate requests to the source system, which increases the load. If
the company has one system for storing basic data, it will receive a huge number of requests. This is often an old monolithic system that businesses want to replace in the future.

Solution

Consumers turn to the storage. The load on the main source is reduced without improving the system itself and increasing resources. When the time comes to replace the old system with several new services, you will need to change the source-storage streams. The changes will not affect many consumers.

The problem

To connect multiple consumers of the same type (for example, retailers), an API is often created within the system. At the same time, the burden that consumers create falls on this system. The inaccessibility of the source system will be a problem for all consumers. They won't be able to get data.

Solution

We create API connectors not inside the service, but as a separate service.  They operate independently of the source system and withstand high loads. You will be able to maintain systems without problems for many consumers.

Data transfer
with the “link” type

To transfer an object with the “link” type, you need to make sure that all directories are created in the consumer system. Otherwise, the object will be created broken or the stream will give an error.
‍
Our connectors check whether the system contract is being fulfilled (completeness, correctness). 
Only when all conditions are met, the message will be sent to the consumer

Assembling the object
from several tables

Object information can be stored 
from several sources. You need to request information on each source and combine it for submission.
‍
Our solution allows you to aggregate object data. For example, collect “orders” and “payments” separately (from different sources) and transfer them as “orders with payments”.

Delete a record
from the tabular part of the object

Such a record is not registered for the 1C exchange. The receiver system must know this feature of 1C and calculate changes on its own.
‍
Our connectors can check deletion from the table. If the deletion took place, mark it 
in storage. Consumers don't have to do calculations.

A snapshot of current prices