Reference architecture - Azure with Data Clients
This reference architecture is intended for deployments to a Microsoft Azure cloud, with support for one or more LinXmart Data Clients.
Topology
Components
| Component | Description |
|---|---|
| Data Client | A headless agent (service) that provides LinXmart access to remote data sources. |
| Source Data | One or more databases containing data required for linkage. |
| Linkage Users | The end users of the system include application administrators, data managers and linkers. Roles and permissions are configurable. |
| App Gateway | An optional load balancer with Web Application Firewall capability. |
| Application/Integration | Orchestration of LinXmart is available through the Web API and allows automation of data workflows in and out of the system. |
| Web App | Hosts the web site that provides a front-end to the users. It will require access to the Azure SQL and the Storage Account. |
| Web API | Hosts the web API that is used by client applications for automation/integration. This is combined with the Web App in one App Service Plan. |
| Worker VM | The linkage processing is performed on this machine and should be provided enough resources to cater for intended data sizes. |
| Entra ID | Entra ID provides the authentication for the system and users must also be explicitly added to LinXmart. Authorisation is handled internally to LinXmart. |
| Key Vault | Storage of secrets and certificates used by LinXmart. |
| Azure SQL | The primary database stores all project configuration, metadata and application settings. Additional databases are created for each linkage project, keeping project data siloed. Serverless databases are supported for the project database. |
| Storage Account | Stores the raw data that is ingested into the system and can store linkage map data downloadable from the Web UI. |