Real-Time
Data is processed close to the time that it is input or needed. This implies that you are processing data fast enough to respond to events as they occur. For example, a customer submits an application for a credit card and you approve it within a few seconds such that they immediately get an answer.Near Real-Time
Data is processed as events occur but not fast enough to respond immediately. For example, a customer submits a credit card application and you immediately begin a process of evaluating the application such that customers often get an answer within an hour.Batch
Data is processed when computing resources are available such that processing falls behind events and catches up. For example, a social media site that runs algorithms to look for policy violations whenever computing power is free. Such algorithms may process posts that are hours or perhaps days old.Custom Job
Batch processing that is unique such that it might be executed once or on an irregular schedule. For example, a batch job that detects a certain type of social media policy violation might be executed once to clean up old posts.Analytical Processing
Processing that is tied to decision making as opposed to business processes and events. This can be done in real-time or near real-time such that decision makers can explore data with analytical tools. It is also common to do analytical processing as batch jobs that produce regular reports.| Overview: Data Velocity | ||
Type | ||
Definition | The speed at which data is processed. | |
Related Concepts | ||
