Calibo Accelerate Microservices
The Calibo Accelerate platform adopts a microservices architecture, wherein each service is responsible for a specific piece of functionality and operates in a separate self-contained unit. For adapter development, you need some of the microservices used by the Calibo Accelerate platform. The details of the microservices are listed below.
System Requirements
The system requirements for using the Calibo Accelerate Microservices are as follows:
| Technology | Details |
|---|---|
| IDE | IntelliJ/VS Code |
| Java version | OpenJDK 11 |
| Spring boot | 2.7.6 |
| Database | MySQL 8.0.3 [Other compatible RDBMS] |
| Gradle | 6.9.2 |
| Docker | 4.22 |
List of Calibo Accelerate Microservices
The following table contains the list of microservices that are used across the Calibo Accelerate platform. Some of these microservices are required for developing an integration adapter.
| Service Name | Description | Required for Adapter Development |
|---|---|---|
| plf-async-log-service | This service is responsible for logging events of asynchronous functionality. | No |
| plf-data-pipeline-designer | This service is responsible for business logic related to data pipeline studio and its functionalities. | Yes |
| plf-databricks-integration | This is façade service to databricks tool. | No |
| plf-alert-service | This service is responsible for alert mechanism of the platform. | No |
| plf-mfa-service | This service is responsible for multi factor authentication functionality. | No |
| plf-qlik-integration | This is façade service to qlik tool. | No |
| plf-agile-integration | This is façade service towards agile tools. | Yes |
| plf-metabase-integration-service | This is façade service to metabase tool. | No |
| plf-secrets-service | This is façade service to secret storage tools. | Yes |
| plf-configuration-service | This service is responsible to hold all platform configurations. | Yes |
| plf-devops-orchestrator-service | This is client agent for communicating with DevOps tools. | Yes |
| plf-admin-service | This service is taking care of onboarding functionality. | No |
| plf-dps-ml-component | This service takes care of machine learning components. | No |
| plf-doc-management-integration-service | This is façade service to document handling tools. | Yes |
| plf-devops-integration | This service is responsible for devops related functionalities. | Yes |
| plf-config-server | This service is responsible for providing runtime configurations for other services. | No |
| plf-collector-service | This service is responsible for data collection form different tools. | No |
| plf-rbac-service | This service takes care of roles and its applicability for authorization in the platform. | No |
| plf-notification-service | This service deals with notification tools. | No |
| plf-orchestrator-service | This is client agent to deal with tools on REST protocol. | Yes |
| plf-common-orchestrator-service | This is client agent for communication with data related tools. | Yes |
| plf-audit-service | This service keeps track of all audit events across all the platform. | No |
| plf-teams-integration | This is façade service to Microsoft Teams. | No |
| plf-elab-service | This is the orchestration service holding core logic of the platform. | Yes |
| plf-workflow-service | This is façade service towards workflow management and its functionality. | No |
| plf-snowflake-integration | This is façade service towards snowflake tool. | No |
| plf-cloud-integration | This is façade service towards cloud aggregators. | No |
| plf-utility-service | This service deals with email activities. | No |
| plf-maturity-assessment-service | This service is responsible for maturity assessment capability of the platform. | No |
| plf-reporting-service | This service keeps the logic for preparing different reports for the platform. | No |
| plf-analytics-service | This service collects and provides analytical data of the platform. | No |
| plf-aiops-service | This service is responsible for co-relating and preparing end reports from collected data using collectors. | No |
| plf-keycloak-adapter | This service is the main service dealing with user authentication and all its functionalities. | No |
| plf-data-browsing-service | This is façade service towards data fetching from cloud accounts. | No |
| plf-management-orchestrator | This is client agent for authentication of platform calls in client side. | No |
| plf-feature-service | This service takes care of feature enabling of the platform. | No |
| plf-ui-poc | This is UI component of the platform. | Yes |
| plf-sagemaker-integration | This is façade service towards sagemaker tool. | No |
| What's next?Integrating Adapters with Calibo Accelerate Orchestrator Agent |
Recommended Topics