Architecture

The Sling Data Platform consists of three main components that work together to provide a scalable and secure data movement solution:

1. Control Server & Database

2. Agents (Self-hosted)

3. Frontend UI

System Overview

Sling Platform Architecture

Control Plane

The Control Plane is the central coordination point of the Sling Platform that:

• Manages user authentication and authorization

• Stores configuration data (connections, replications, etc.)

• Coordinates job scheduling and execution

• Maintains system state and job history

• Communicates with agents via secure NATS websockets

• Provides REST API endpoints for the frontend UI

Agents

Agents are distributed workers that:

• Run the Sling CLI to execute data jobs

• Operate within your infrastructure for secure data access

• Connect to the Control Server via secure NATS websockets

• Can be deployed across multiple environments (dev, prod, etc.)

• Scale horizontally to handle increased workload

• Provide secure access to data sources without exposing credentials

Frontend UI

The Frontend UI provides:

• Web-based interface for managing Sling operations

• Secure communication with Control Server via HTTPS

• Visual workflow creation and management

• Real-time monitoring and alerting

• Team collaboration features

• Connection management interface

Communication Flow

1. Users interact with the Frontend UI over HTTPS

2. Frontend UI communicates with Control Server via REST API

3. Control Server coordinates with Agents using NATS secure websockets

4. Agents execute jobs and report status back to Control Server

5. Control Server updates Frontend UI with job status and results

Security

• All communication between components uses encryption (HTTPS, WSS)

• Agents run in your infrastructure, keeping sensitive data and credentials secure. No ports need to be opened.

• Authentication and authorization managed by Control Server

• Credentials stored securely in Control Server database, or on your self-hosted agent.