Architecture
Datalogic Connect is built on a modern microservices architecture that provides scalability, flexibility, and reliability for managing your devices and data. The platform is designed to handle large volumes of data, support real-time analytics, and integrate with a wide range of Datalogic devices.
High-Level Architecture
The diagram below shows the overall architecture of Datalogic Connect: operators manage devices from a centralized cloud, while each store runs an IoT Edge Gateway that bridges the cloud and local Datalogic devices.
For further information about security, please see the DL Connect - Security Prospectus.
Components Overview
| Component | Description |
|---|---|
| Web Application UI | User-friendly interface for monitoring and managing devices, stores, and users across all locations. |
| REST API | Primary communication layer between the UI and backend services. Handles data exchange and control commands. |
| IoT Edge Gateway | A server deployed in each store that bridges the cloud and local devices. Runs IoT Edge modules for message routing, certificate management, and file serving. |
| AladdinSDS | Software installed on each POS system that manages communication between the POS and connected Datalogic devices via the appropriate driver. |
| Mobile Scanners | Datalogic mobile devices that connect directly to the IoT Edge Gateway over MQTT (plain, port 1883) or MQTTS with mutual TLS (port 9883). |
| USB Devices | Datalogic fixed retail scanners and handheld scanners connected to a POS system via USB interface and managed through AladdinSDS. |
Workflow Summary
-
Cloud Communication: The Web Application UI interacts with the Datalogic REST API to issue commands and retrieve data. Commands and telemetry are transmitted securely over the Internet using MQTT or HTTPS.
-
Store Communication: The IoT Edge Gateway in each store receives messages from the cloud and routes them to the appropriate POS system over the local network.
-
Device Interaction: Each POS system communicates with connected IoT devices through the AladdinSDS and device driver. Devices execute commands or return telemetry data back through the same path.
Network Requirements
To ensure proper communication between your IoT Edge device and Datalogic Connect services, make sure the following network endpoints are accessible:
| Endpoint | Port | Protocol | Notes |
|---|---|---|---|
*.azure-devices.net | 8883, 443, 5671 | MQTT TLS, AMQPS, or HTTPS | Send diagnostic data, receive cloud commands (edgeHub upstream) |
global.azure-devices-provisioning.net | 443 | HTTPS | Device provisioning |
*.blob.core.windows.net | 443 | HTTPS | File upload, Docker image pull |
crsolinfraprodeuw.azurecr.io | 443 | HTTPS | Container registry |
crsolinfraprodeuw.westeurope.data.azurecr.io | 443 | HTTPS | Container registry (data endpoint) |
*.azureiotcentral.com | 443 | HTTPS | Device Smart Enrollment |
If your device is behind a corporate firewall, ensure all outbound endpoints above are whitelisted. The IoT Edge runtime will automatically select the best available upstream protocol (MQTT TLS on 8883 or HTTPS on 443).
Local Inbound Ports (Field Devices → Edge Device)
The following ports must be reachable from Datalogic field devices or AladdinSDS on the local network:
| Port | Protocol | Service | Used by |
|---|---|---|---|
1883 | MQTT (plain TCP) | NanoMQ | PCs, POS systems, HOST-type devices |
9883 | MQTT over TLS (mTLS) | NanoMQ | Datalogic scanner devices with client certificates |
8090 | HTTP | StorageModule | Field devices downloading firmware/config or uploading logs |
8098 | HTTP | ProvisioningModule | Field devices requesting X.509 certificates |
Key Features
- Centralized Management: Cloud-based monitoring and control of IoT devices across multiple stores from a single interface.
- Real-Time Communication: MQTT ensures efficient and reliable message delivery between the cloud and stores.
- Scalability: Additional stores and devices can be onboarded without significant architectural changes.
Use Cases
- Retail Operations: Managing point-of-sale systems and associated IoT devices across a retail network.
- Device Monitoring: Centralized oversight, diagnostics, and health tracking of IoT devices.
- Remote Configuration: Deploying firmware updates and configuration changes to stores from the cloud.