In all previous chapters, we have worked with batch-type job objects in Data Services. As we already know, a batch job in Data Services helps to organize ETL processes so that they can be started on demand or scheduled to be executed at a specific time either once or regularly.
The main difference between a real-time job and batch job is the way these two job objects are executed by Data Services engine. The purpose of a real-time job is to process requests providing response. So, technically, a real-time job could be running for hours, days, or even weeks without actually processing any data. Data Services engine actually executes the ETL code from within the real-time job object only when new request comes from an external service. Data Services uses this request message as the data source, processes this data, and sends the processed data back to external service in form of response message.
A new Data Services component called Access Server has come into the frame. Access...