Data Spine Admin Guide
Deployment and Configuration
The sequence in which the components of Data Spine should be deployed and configured:
- EFS (Keycloak and Policy Enforcement Service)
- Integration Flow Engine (Apache NiFi)
- Message Bus (RabbitMQ)
- Service Registry (Linksmart Service Catalog)
- API Security Gateway (Apache APISIX)
Follow the documentation of individual components for deployment, configuration and maintenance
Data Spine Components' Interaction
Figure 1: Data Spine Components' Interaction
Figure 1 illustrates the technological platforms, tools and services selected to realise different components the Data Spine and the interactions between them. The figure also shows Service Provider providing service S1 through the Data Spine and Service Consumer’s service S2 consuming S1 through the Data Spine with the help of ‘Integration Flow 1’.
In this way, the Data Spine provides the necessary integration infrastructure to bridge the interoperability gaps between heterogeneous services and enables communication in the EFPF ecosystem.