Core Auto Architecture | Robust and Scalable Automation Framework

Core Auto Architecture

Core Auto's architecture is designed to facilitate seamless process automation across distributed
environments. It consists of key components that manage, monitor, and optimize processing
workflows in real-time and batch environments.

Core
Components

Collector

The Collector serves as an interface for external systems to interact with Core Auto. It provides endpoints for generating events, setting flags, and retrieving stored credentials. External systems authenticate through technical users defined in the GUI, and logs are generated for all interactions.

Manager

The Manager controls all processes executed within Core Auto. It starts workers (CAwrkr) and serves as a throttling mechanism by limiting the number of concurrent processes. The Manager oversees both batch and real-time tasks, ensuring adherence to dependencies and execution paths, including the global critical path.

Agent

The Agent is a remote component installed on servers other than the Loading Node. It enables the execution of specialized tasks requiring software available only on those servers. Agents handle worker initialization, communicate with the Manager via PostgreSQL mechanisms, and can interrupt processes during deadlocks or other emergencies.

Worker

A Worker in Core Auto is a process that executes individual steps as defined in the system's metadata. Each worker can handle one step at a time, ensuring efficient execution and adherence to dependencies. Workers are initialized by the Manager and can run on the Loading Node or remote hosts equipped with Core Auto Agents. They are pivotal in both batch and real-time processing, maintaining seamless integration across distributed environments.

Core
Components

Collector

Manager

Agent

Worker

Data Flow and Processing

Core Auto’s data flow is optimized to reduce process execution times by focusing on the critical path. It defines two types of critical paths:

Global Critical Path (GCP):

The longest sequence of dependent steps, ensuring minimum completion time for all required processes.

Local Critical Path (LCP):

A custom path defined by administrators to prioritize specific steps, even if they don’t belong to the GCP. This flexibility allows Core Auto to dynamically optimize workflows based on operational priorities.

Security and Authentication

Core Auto uses secure, role-based access for process and data management.   

External systems authenticate through the Collector using limited-privilege technical user credentials.   

All credentials are securely managed within the KeyStore and accessed via one-time tokens for additional security during process execution.

Deployment Requirements

Operating System:

UNIX/Linux

Database:

PostgreSQL (version 12.3 or later)

Hardware Requirements:

2 vCPU, 4 GB RAM, and 1 GB storage  (plus additional space for logs)

Security and Authentication

Core Auto supports batch and real-time processing.   
In batch mode, Core Auto activates daily tasks, such as feeding data from source systems to data warehouses. In real-time mode, the system responds to external events to initiate relevant workflows. This dual-mode capability enables Core Auto to support complex, interconnected processes efficiently.

view demo