How sovity/edc-ce works
Project type and purpose
• This is a full‑stack, self‑hostable “Connector” application built on Eclipse Dataspace Components (EDC).
• The backend (under connector/…) is a modular EDC Connector (Control Plane + optional Data Plane) extended by Sovity for enterprise‑ready features (DAPS integration, vault, messaging, DB migrations, etc.).
• The frontend (under frontend/…) is a Next.js/React UI that talks to two HTTP API surfaces exposed by the Connector:
a. A “UI API” for driving the web‑based dashboards and CRUD operations.
b. The “Management API” for integration and automation.
High‑level file‑structure analysis
• Top‑level directories:
• connector/… – Kotlin/Java Gradle projects for CE Connector, Docker image definitions, multiple library modules (api, json‑ld, mappers, runtime, runtime‑os, runtime‑test).
• frontend/… – Next.js UI, API‐client generation, fake‐backend for local dev, static assets, environment configs.
• docs/… – Documentation of Management API, UI, deployment, backend use cases.
• Key backend sub‑areas:
• connector-ce/src/main/kotlin/de/sovity/edc/ce – entry point CeMain, DI modules for Control Plane and Data Plane.
• api/…/control + api/…/ui – REST controllers for Control‑plane operations and the UI.
• modules/… – plugin‑style modules: db, vault (HashiCorp or in‑memory), messaging (contract terminations, data‑plane registration), auth (API key, OAuth2), dataspace features.
• utils/db‑schema‑ce – Flyway migrations.
• Frontend sub‑areas:
• src/app – Next.js pages and API routes (/api/health).
• src/lib/api – generated TS client + fake‑backend implementation for local dev.
• src/components – shared UI components, forms, tables, dialogs, policy editor, etc.
Insights from README
• The Connector is packaged as Docker images (control plane, optionally integrated data plane).
• The UI runs independently (Node/Next.js) or can be served via static build.
• Standard requirements: Java 17, Node 20, Docker.
• CI/CD provided via GitHub Actions building connector images and UI images.