Divante ESB Data bus
Divante ESB Data bus
The main factor for the success of Omnichannel Sales is efficient and fast exchange of information. ERP, PIM, eCommerce, CRM and WMS systems have to transmit information about inventory and product orders on an ongoing basis. Delays or lost messages can have a very far-reaching consequences – that’s why we created Divante ESB Data Bus.
The data bus is comprised of four main elements:
- API – a ready-made module that creates a generic API that is used to send data to the bus, based on data description. The module performs sender authentication and data structure basic validation.
- Queues – a message received by the API is placed in a queue and waits for free resources that will process the message. This can control the amount of messages entering a given system.
- Workers – each queue is supported by workers – processes whose task is to take a message from the queue and send it to an appropriate system waiting for it. In the case of unsuccessful action on the side of the outside system there may be any logic: an attempt to re-send, send the message elsewhere, delete it, or move it to be processed later.
- Flows – this module allows for configuring the message flow through the system. It provides a simple way to determine how the message should be received, of which structure, which workers should handle it and what should be their logic.
Data bus is licensed to allow further development of the software on the client side without Divante. There is no vendor lock-in because the implementation price includes developer license with full source code.
Figure 1. Integration through the ESB is primarily aimed at minimizing the amount of integrations and being open to new systems. The number of connections is lowered from N*N to 2*N (where N is the number of systems)
Divante data bus can be integrated with any input and output data format with dedicated connectors (code in Java).
The following formats are supported by default:
- OAGIS (Open Application Group Integration Specification) — a non-profit organization, which aims to create a standardized description for objects that can occur in business processes. This standardized format for XML messages can be used for most of the solutions in systems integration.
- EDI (Electronic Data Interchange) — it is also one of the standards of forming messages that can be passed between systems. The purpose of EDI is to eliminate the re-keying of data and increase the accuracy of the information flow.
- SQL — integration with MSSQL, Oracle, PostgreSQL, MongoDB and MySQL databases via a connector that allows running SQL queries, and downloading data from views and stored procedures,
- CSV — integration with a simple text file format where the values are separated by a separator,
- XML / XML RPC — integration with any XML pattern transmitted in the form of files, WebServices call or e-mail,
- REST — integration with any data source via http protocol.