Real-time Server

All Environments

The Real-time Server hosts several components:

A Talend Remote Engine is used to deploy real-time artifacts – Data Services and Routes. Unlike on the Batch Server, the Talend Remote Engine plays no role in the execution of these artifacts. It does monitor their execution and provides information back to Talend Cloud, such as logs.
Artifacts can be deployed either to a Talend Runtime (must be co-located on same server) or as a standalone Microservice (again on same machine)
Currently this guide shows both deployment mechanisms, as the mechanism of choice depends on what you are implementing. Longer term it is expected that microservices will be the mechanism of choice, but that is not true for all use cases today. The most notable use case is for a Data Service or Route that has a dependency on a pooled database connection – today this can only be achieved with Talend Runtime, it is on the road-map for microservices. Generally microservices have benefits for auto-scaling patterns (road-map) and they avoid the need for regression testing that occurs when deploying a new version of the Runtime.

Note the separation of concerns – heavyweight batch jobs that run periodically impact the performance of our real-time services, and this is best to be avoided. If only very light usage is made of batch jobs or real-time services, you could avoid the need for deploying the two execution servers, but the Reference Architecture recommendations are made based on typical enterprise usage patterns.

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!