Experimental
Warning
As of v0.7.0, the services explained in this section are still experimental and not yet used as the default. These services are part of an ongoing migration and are not the supported way of working with the platform yet. Their APIs, schemas and behaviour may change until they are stabilized. For users and developers who want to use Kaapana in production, please keep following the supported documentation in the other sections.
Kaapana is transitioning from a set of monolithic, kaapana-backend centric components towards a collection of targeted and single-purpose APIs.
The goal is to make the platform more scalable, modular, decentralized, easier to maintain.
During this transition, both the legacy (supported) and the new (experimental) implementations can be found in the platform.
This page gives an overview of how these new services function as main pillars of the platform’s architecture, the sub-pages document each new service in detail.
Old vs. new services
Domain |
New (experimental) |
Old (supported, still the default) |
|---|---|---|
Workflows |
workflow-api: engine-agnostic REST API for workflows, revisions and runs |
|
Tasks / processing containers |
task-api: a contract and library for running processing containers (already usable today) |
DAG operators based on |
Data |
data-api: |
|
Extensions |
extension-manager: OCI-based
extensions (service, UI and |
|