According to our observations, 90% of business cases
builds an IT architecture with critical flaws,
which results in a number of complications

We build IT infrastructure using ESB and data lake
due to the weak connectivity of IT systems,
that solves all of the above problems!

Profitability

Failures in building IT infrastructure are not so noticeable at the beginning, but are extremely harmful during further development

IT infrastructure

Exit — build service-oriented IT architecture based on an enterprise service bus (ESB) and data lake through an approach weak connectivity IT system modules

It's like an interpreter who can always hear
will understand and explain clearly

And can communicate with a whole group of tourists from different countries —
without any delays and with everyone at the same time!

Let's look at specific examples,
like implementing ESB and data lake:

1)
eliminates data loss;
2)
reduces the load on the IT system;
3)
simplifies data analysis;
4)
ensures easy replacement of IT systems

1. ESB itself controls the availability of the system and network, picks up and delivers messages by itself

1.
The load on systems is reduced
2.
Data loss is avoided
3.
The relevance and duplication of data are checked
which also reduces the load on infrastructure

2. The combination of ESB and data lake makes analytics easy

1.
ESB combines data from different systems and brings them to a single standard in DWH. DWH stores parsed data so you can easily and quickly obtain standard slices
2.
Data lake, unanalyzed data from all enterprise systems, allows you to prepare any data slice
3.
The relevance and duplication of data are checked, which also reduces the load on the infrastructure. Adding new data sources is easy, and replacing the BI platform will not require complicated reconfiguration

3. It is always easy to get a retrospective of messages and prepare a full analysis of the incident in the event of a failure

4. Easy migration from one IT system to another of the same type, since all the integration logic has already been implemented in middleware

5. Due to a single middleware layer for all systems connected to ESB, the load is reduced by orchestrating streams

Stream orchestration

Optimizes and drastically reduces the load
for IT systems

Sends data only to those who need it, and only in the form that is needed
It takes into account optimal shipping conditions:

— time based on system load,
— duplicate control,
— taking into account the relevance of data

We have developed a targeted system integration scheme for a manufacturing enterprise. We implemented ESB technology and launched 48 streams

Point A
EKF does not have an up-to-date map of IT integrations, system connectivity is strong, the central ERP is overloaded, and lags and data losses may occur, which slows down business processes.

Point B
A centralized system based on Pimcore, integrated via WSO2 ESB, has been implemented. Product cards are standardized, data is synchronized automatically, and can be scaled and controlled through message brokers and a logging system.

We have developed a single API for quick connection of over 200 “1C:Retail” systems

Point A
Polaris manages goods manually, which requires significant resources and makes it difficult to interact with marketplaces due to data silos.

Point B
A centralized system based on Pimcore, integrated via WSO2 ESB, has been implemented. Product cards are standardized, data is synchronized automatically, and can be scaled and controlled through message brokers and a logging system.

We have developed a single API for quick connection of 200+ 1C:Retail systems

Point A
The point-to-point integration architecture between 1C:ERP Enterprise Management and more than 200 1C:Retail systems has led to overloads, irrelevant data and lack of transparency.

Point B
The introduction of a single API connector has essentially made it easier to synchronize data by eliminating multiple point connectors. Adding new outlets is now quick, and monitoring ensures transparency and control.

A supplier portal was developed for the Fix Price network and automated the work with product data

Point A
Manual collection and transmission of product data via messengers and email, which led to errors and delays. Problems with synchronizing data between systems.

Point B
Automation via Pimcore and Mule ESB. In their personal account, suppliers enter data that is automatically transferred to systems, thereby improving the quality and speed of their processing. The ESB bus makes it easy to integrate and manage data.

We redesigned the IT architecture and drew up a roadmap for its transformation for music retailer Muztorg

Point A
Muztorg has problems with its outdated IT architecture, which result in high maintenance costs, inefficient system interaction and risks of data loss.

Point B
A new architecture has been developed with the introduction of MDM and ESB solutions, which makes it possible to optimize the operation of information systems, ensure scalability, improve data quality and accelerate integration with external services.

We introduced a scalable service tire for ATIMO

Point A
The startup ATIMO faced the problem of scaling its system. Each new counterparty required a direct connection to the database, which led to significant resource costs and increased information security risks.

Point B
The introduction of a service bus (ESB) has made it possible to simplify the connection of taxi fleets, speed up data processing, reduce the load on servers, and increase security by eliminating direct connections. The architecture became easily scalable, which made it possible to connect 20 taxi fleets with 42 databases and significantly reduce the amount of resources required to complete each request.

Leave a request to review your situation:

We will select proven international products
open source

We use Opensource solutions, so our customers reduce license fees without the risk of restrictions from legislation in different countries.

Graphic studio
for creating connectors

A simple and flexible low-code platform that is part of Salesforce with revenues of more than $30 million per year. We're using the Community Edition.

Version control and setup
access rights (roles)

An open source, web-based DevOps lifecycle tool. More than 30 million registered users.

Database
(storage)

A powerful open-source object-relational database system that has been actively developed for over 35 years.

Storage, analysis,
search by logs

Enterprise security, surveillance, and search solutions built on the Elasticsearch platform used by thousands of companies.

Information dashboards
about the state of flows

A system for visualizing and analyzing information that allows you to work “out of the box” with a wide range of data sources.

2
/

If you have preferences, we can also use other products. Including with a paid license

Typical work scheme

We have designed the implementation process so that you get the most out of it. You can go all the way with us. Or order any of the steps separately and hand over the rest to your team.

1. Designing a low coupled architecture

  • We will analyze the current IT architecture, ASIS;
  • We will work out exchanges on key entities;
  • We will design the TOBE architecture;
  • We will prepare a roadmap for the transition to the new architecture;
  • We will prepare recommendations; on tools;
  • We will prepare documentation.
Location Icon
You'll get

The transition plan, taking into account
business features

2. Migrating the streams that are most relevant to you

  • BPMN schemes of flow processes;
  • Deploy and configure the required components
(ETL, storage, logging, monitoring);
  • Configuring connectors;
  • Setting up log collection and monitoring the integration;
  • Documentation and training.
Shield Icon
You'll get

Solving 80% of data exchange problems between systems

3. Migrating the rest of the streams to fill the data warehouse

  • BPMN schemes of flow processes;
  • Configuring connectors;
  • Setting up log collection and monitoring the integration;
  • Documentation and training.
Gear Icon
You'll get

A single mechanism for exchanging the entire enterprise and the completeness of data for analytics

Project calculator

Development cost
5,775,000 rubles
The team will develop for
6 weeks
Included in the calculation
Cross or Plus Icon
  • Preparation of a map of systems and data flows (SOA scheme);
  • We will work out exchanges on key entities;
  • Creating connectors for exchanging data for each stream on 3 stands (test, preprod, prod);
  • Setting up to three dashboards per connector within a ready-made monitoring circuit;
  • Documentation on copying integration, reusing, and maintaining;
  • Demonstration of the implemented functionality.
Additional works
Cross or Plus Icon
  • Preparing the infrastructure for connectors to operate;
  • Setting up the monitoring and logging circuit;
  • Creating connectors (storage - receiver) for exchanging data on each high-load stream (>100 messages per minute) on 3 stands (test, preprod, prod);
  • More than 15 attributes for each stream;
  • The cost of computing resources (subscription only);
How many streams will the systems send

Example: The “Product Management System” will send product data. “Order Management System” — about orders. “Warehouse management system” — about the status of the shipment. This is 3 streams.

0
0
100

Example: The “Warehouse Management System” will receive data on goods and orders. “Order Management System” — about goods and shipment status. This is 4 streams.

How many streams will the system receive
0
0
100
Discuss the project

The calculator calculates using an accurate but simplified formula. The scope of work for your project and the final cost may vary. The final calculation will be made by your personal manager.

Discuss the project

The calculator calculates using an accurate but simplified formula. The scope of work for your project and the final cost may vary. The final calculation will be made by your personal manager.

youtube

We are talking about integrations on YouTube-

channel

See all
Integration of the IT infrastructure of an e-commerce project with marketplaces using the WSO2 ESB service bus

Integration of the IT infrastructure of an e-commerce project with marketplaces using the WSO2 ESB service bus

Integration of Talend ESB into the IT infrastructure of a logistics company

Implementation of the Talend ESB service bus into the project's IT architecture

Visit our bot for prompt advice and useful information