NExt generation Meta Operating systems (NEMO) and Data Space: envisioning the future
summary
NEMO claims to host Data Space Connectors as plugins and actually implements a prototype Fiware-based Industrial Data Space Connector that bundles an Orion Context Broker into the metaOS and is provisioned via an intent-based API. Workload descriptors carry monetization, security and dependency metadata; provisioning enforces validations and creates tokens. Access control extends beyond auth to blacklisting and rate limiting. Prototype integration exists but full validation and commercialization checks remain future work.
AI-written summary · about
chapters (8)
- 0:00NEMO and data spaces intro
- 1:26Cloud-edge-AI integration challenges
- 3:57Data spaces for EU governance
- 6:27Fast NEMO dev and deployment
- 8:11NEMO architecture layers
- 10:20Onboarding data space connectors
- 12:11FIWARE Orion case study
- 13:57Conclusion and future validation
related talks
29mOneNet Framework - Open Data Space Solution for Energy Digitali...
17mApache Nemo: A Framework for Building Distributed Dataflow Optimization Policies
20mData Mesh, Data Fabric & Co - the End of Monolithic Architecture Concepts?
27mData Mesh for the Cognitive City
17mEnabling Compute and Data Sovereignty with Infrastructure-Level Data Spaces
17mComposable Data Management Systems
38mData Mesh, Now
31mData Mesh, Next