LogoLogo
How to Build Dataspaces?Main IDSA AssetsOther ResourcesManifesto for International Data Spaces
OPEN DEI Building Blocks Catalog
OPEN DEI Building Blocks Catalog
  • Building-Blocks-Catalog
  • Access and usage control
  • Business building blocks
  • Continuity model
  • Data Exchange APIs
  • Data Models and Formats
  • Data Usage Accounting
  • Identity Management (IM)
  • Metadata and Discovery Protocol
  • Organisational/operational building blocks
  • Provenance and traceability
  • Publication and Marketplace Services
  • Trusted Exchange
  • other_building_blocks
    • Data Analytics Engine (DAE)
    • Data Processing
    • Data Routing and Preprocessing (DR&P)
    • Data-, Service-, Privacy- and Monitoring.
    • Data Visualization
    • Marketplace Data Lifecycle Process
    • System Adaptation
    • Workflow Management Engine (WME)
  • Contributing to Building Blocks Catalog
Powered by GitBook

Links:

  • IDSA Website
  • IDSA Github
  • Legal Notice
  • Privacy Policy

© 2016 – 2025 | All Rights Reserved | International Data Spaces Association

On this page
  • Definition
  • Role and Scope
  • Features
  • Components and Technologies
  • Technical Reference Implementation
  • Business Use Cases Implementation
  • Best practices identification and recommendations
  • Gap or what is missing?
  • TRL
  • Comments
  • Additional Information
Edit on GitHub
  1. other_building_blocks

Data Routing and Preprocessing (DR&P)

Definition

There may be a need for dynamic routing of data to the proper data-processing node (as part of a dynamic data-routing function). The building block for data routing and preprocessing is usually a data middleware platform (or a combination of two or more such platforms). These address different technical requirements, depending on the nature of the data that is collected and routed (e.g. streaming data, data at rest).

Role and Scope

Features

Components and Technologies

Design Principles Position Paper
  • Stream-processing middleware platforms (e.g. Apache Kafka) can be used to support the routing and preprocessing of streaming data.

  • Horizontal and vertical scalability.

  • Aspects esulting from data usage policies, like jurisdiction for data processing, data egress, or combination with other data.

Technical Reference Implementation

Business Use Cases Implementation

Best practices identification and recommendations

Gap or what is missing?

TRL

Comments

Additional Information

Last updated 1 year ago