Skip to content


This section aims to briefly describe the Platform architecture, listing and detailing each component of the ODM Platform.

The following image depicts a diagram of the architecture.



API names in the Product Plane do not necessarily exhibit what's implemented in the application. The only purpose here is to show each module's capabilities.

As you can see, the architecture is composed of two planes reflecting those proposed by Data Mesh theory:

  • Product Plane: the ODM implementation of the Data Product Experience Plane, which helps to build and consume data products, as well as managing their entire lifecycle.
  • Utility Plane: the ODM implementation of the Data Infrastructure (Utility) Plane, which aims to decouple the data product management from the underlying physical infrastructure.

It turns out that the ODM Platform main modules are technology-independent: data products are created and managed via the Product Plane independently of the underlying physical layer, which is decoupled by the Utility Plane and the Adapters.

Product Plane⚓︎

The Product Plane exposes the core microservices of the ODM Platform. Each microservice offers a set of APIs to deal with every phase of the data product lifecycle. ODM Platform uses the Data Product Descriptor to create, deploy and operate the data product instances in the mesh architecture.

The Product Plane provides the following set of microservices:

  • Blueprint Microservice: it handles data product bootstrap and initialization leveraging on a deep integration with Git services.
  • Registry Microservice: it registers a new data product with a unique identifier and a data product version within the mesh, making it visible to the mesh governance processes.
  • Policy Microservice: it handles services to apply and run embedded computational policies on every data product of the mesh.
  • DevOps Microservice: it manages the entire data product lifecycle (i.e., development, test, deploy, decommissioning).
  • Notification Microservice: it manages listeners and dispatches notifications upon events reception.
  • Params Microservice: it is a custom ODM microservice to handle common parameters and variables within the entire platform.

Each microservice is ready to use and represents an available feature of the platform.

Utility Plane⚓︎

The Utility Plane exposes a set of services useful for the mesh functionality and infrastructure decoupling, like:

  • Executors: they act as a proxy between the mesh platform and specific DevOps tools.
  • Observers: they collect and react to events occurred in the mesh platform.
  • Validators: they are services dedicated to the evaluation of computational policies.

Each microservice exposes an interface requiring a real implementation of it. The aim here is to give a starting point and a blueprint structure for the realization of the specific services. Any implementation of the Utility Plane services is called Adapter.


An Adapter is a technology-specific implementation of the Utility Plane services: it is the component that decouples the mesh platform from the real infrastructure.

Each Adapter is pluggable to the ODM Platform via configuration properties. ODM users are required to configure all the adapters they need to work with the underlying infrastructure layer.

ODM Platform offers an implementation of the following Adapters:


ODM Platform is a multi-module Java application composed of multiple microservices. The following is the list of the development technologies:

  • Java
  • Maven
  • Spring
  • Spring Boot

All the services make use of this set of technologies as a baseline. Each single service can employ additional tools to meet different needs.