Implementing an ESB layer based on Talend - KT.team

Accelerate integrations
with Talend ESB

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.

What tasks can be done with Talend ESB

1

Implementation of integration interactions

between systems.

2

Creating scripts

for filling in data (for example, migration scripts).

3

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).

4

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).

Talend ESB features

1

Routing

Learn more about Talend ESB features - KT.team
Flow routing in Talend - KT.team

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

Learn more about Talend ESB features - KT.team
Data conversion to Talend ESB - KT.team

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

Learn more about Talend ESB features - KT.team
Easy scalability in Talend ESB - KT.team

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

Learn more about Talend ESB features - KT.team
Talend ESB as a self-documenting system - KT.team

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).

Is there a need for implementation?

Contact us and we will calculate the time and cost of implementing the ESB system

The difference between Talend and classic development

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's main advantage is the low-code approach

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.

The advantage of Talend ESB is a low-code approach to developing integrations - KT.team

ESB system implementation cases

Watch all

Watch all

Is there a need for implementation?

Contact us and we will calculate the time and cost of implementing the ESB system

YouTube

We have collected all the mistakes in integrations,
for you not to
make them

Watch all
IT consulting for medium and large businesses | KT.team

System integration calculator (ESB)

System Integration Project (ESB) Calculator

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
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
100
How many streams will the system receive
Example: The “Warehouse Management System” will receive data on goods and orders. “Order Management System” — about goods and shipment status. This is 4 streams.
0
Example: The “Warehouse Management System” will receive data on goods and orders. “Order Management System” — about goods and shipment status. This is 4 streams.
0
100
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

Learn more about Mule ESB features — KT.team
Creating and hosting services on Mule ESB — KT.team

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

Learn more about Mule ESB features — KT.team

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 into account

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

Let's discuss your project

Personal managers will contact you

Contact form

Something went wrong! Please try again.
Your application has been sent successfully!

Submit again

Something went wrong! Please try again.

Contact us

Make an appointment

Book a meeting with Google Calendar

We write articles for our blog and for specialized publications

Read more

Talend implementation cases in enterprise projects: global experience

Learn more

Why are techies against data buses: middleware, ESB, message brokers?

Learn more

How to choose the right type of integration for your IT architecture

Learn more

Watch all

We use cookies to provide the best site experience

Ok