Accelerate integrations with Talend ESB
Talend ESB is a universal tool for the rapid integration of services and applications. Installing and configuring Talend allows developers to focus on the project's business logic rather than on complicating technologies.
Implementation of integration interactions
between systems.
Creating scripts
for filling in data (for example, migration scripts).
Enrichment of systems
(for example, in a situation where you need to take data from several systems and send the result to the final system).
Performing non-core tasks
to create simple services (for example, from the point of view of the ratio of time spent and the result obtained, it is more profitable to implement the functionality on Talend instead of writing a service in Python).
1
Routing
The Talend ESB-based service bus makes it possible to send messages in different ways, depending on their content and in accordance with specified rules. You can filter and combine messages and reorder them as needed. Talend can independently receive data from one system using a common API and transfer it to other systems.
2
Data conversion
Inside Talend ESB, you can set up rules for converting messages from one system to be sent to other systems. At the data service bus level, one stream can be checked, parallelized, converted in different ways and sent to the appropriate systems.
3
Scalability
The enterprise service bus has its own mechanisms for planning and distributing the load, with which you can customize the individual logic for receiving and sending data from different systems and applications and monitor their load. For example, if your CRM can accept 100 transactions per minute during the day and 500 transactions per minute at night, ESB will take this logic into account and will not overload your systems.
4
Self-documentability
All messaging actions in Talend are visualized and easy to understand. If you follow the basic rules of naming, any business analyst can quickly figure out how integration works and what needs to be changed. At the same time, the integration code can be packaged and deployed in a stand-alone service (JAR or Docker image).
Parameters
Talend ESB
Classic development
Basic settings
You don't need to write code to implement the Talend job — you can use ready-made components. Main job: setting up logic, transforming and transforming data.
In the case of classical development, when writing code, it is necessary to provide an opportunity to expand the solution, to consider an exchange protocol with a database or between systems. Individual components are often not boxed functionality, but require a custom solution.
Additional functionality
Talend requires testing, building and hosting, but its advantage is that it provides its own ready-made tools for this purpose. We have a choice: use Talend hosting or our own.
The code must be tested, built, and hosted.
Entry threshold
Even those who have never programmed can understand Talend ESB. To complete tasks, it is enough to explain the basic concepts to a person. For example, using the Data Mapper tool, a business analyst can independently perform tasks related to converting documents from one format to another.
You don't need to write code to implement the Talend job — you can use ready-made components. Main job: setting up logic, transformation and data transfoming.
Talend ESB allows developers to configure jobs, each of which is responsible for a specific functionality, without wasting time writing code.
The Talend ESB service bus is a tool for business analysts and project managers. Thanks to it, managers can independently, without involving developers, perform simple tasks, such as converting from one file format to another.
Watch all
A supplier portal was developed for the Fix Price network and automated the work with product data
Learn more
We have developed a single API to quickly connect 200+ 1C:Retail systems
We have developed a single API to quickly connect 200+ 1C:Retail systems
Learn more
Integration of Kafka into the project's enterprise infrastructure
Integration of Kafka into the project's enterprise infrastructure
Learn more
Watch all
We have collected all the mistakes in integrations,
for you not to
make them
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.
Калькулятор считает по точной, но упрощенной формуле. Состав работ по вашему проекту и конечная стоимость могут отличаться. Итоговый расчет сделает ваш персональный менеджер.
1
Calculation example
To transfer data between systems, we create a “stream”. Some streams are needed to send data, while others are needed to receive data. Orders, goods, or other entities may be transferred in a separate stream.
For example, on the diagram:
1. The “Merchandise Management System” sends goods. “Warehouse management system” is the fact that an order has been shipped. “Order Management System” — orders. In total, the systems will send 3 streams;
2. The Warehouse Management System accepts goods and orders. “Order management system” — goods and the fact that the order has been shipped. In total, the systems will receive 4 streams.
2
Scope of work in the calculator
Included in the calculation
Additionally
Preparing a map of systems and data flows (SOA scheme)
Preparing the infrastructure for connectors to operate
Development of object logic (connector business process diagram)
Setting up a monitoring and logging loop
Creating connectors for exchanging data for each stream on 3 stands (test, preprod, prod)
Creating connectors (storage - receiver) for exchanging data on each high-load stream (>100 messages per minute) on 3 stands (test, preprod, prod)
Set up to three dashboards per connector within a ready-made monitoring circuit
Over 15 attributes per stream
Documentation on copying integration, reusing, and maintaining
Demonstration of the implemented functionality
Included
Preparing a map of systems and data flows (SOA scheme)
Development of object logic (connector business process diagram)
Creating connectors (source - storage, storage - receiver) for exchanging data on each object on 3 stands (test, preprod, prod)
Set up to three dashboards per connector within a ready-made monitoring circuit
Over 15 attributes per object
Additionally
Preparing the infrastructure for connectors to operate
Setting up a monitoring and logging loop
Creating connectors (storage - receiver) for exchanging data on each high-load object (>100 messages per minute) on 3 stands (test, preprod, prod)
Over 15 attributes per object
Your application has been sent successfully
Submit again
Personal managers will contact you
Contact us
Make an appointment
Book a meeting with Google Calendar
Read more
Is a message broker always needed?
Learn more
Point to point, broker, ESB: what integrations will help build a loosely coupled IT architecture
Learn more
The properties of a flexible and scalable IT infrastructure: an educational program on basic concepts and the main evaluation criteria
Learn more
Watch all