How eclipse-tractusx/portal-backend works
Project Type & Purpose
• It’s a set of loosely coupled microservices (Administration, Registration, Marketplace Apps, Marketplace Services, Notifications, Maintenance, Mailing, Provisioning, etc.), each exposing a Web API.
• A background “Processes.Worker” executes long-running or asynchronous domain processes via pluggable executors.
• A central relational database (or databases) is managed via EF Core migrations (PortalBackend.Migrations, Provisioning.Migrations).
• Shared functionality is extracted into internal “framework” and “externalsystems” libraries and published as NuGet packages.
• Integrates with external identity and trust systems: Keycloak (IAM), BPDM, BPN DID Resolver, Custodian wallet, DIM, Clearinghouse, Issuer, OfferProvider, OnboardingServiceProvider.
File Structure & Architectural Patterns
• src/<service> directories: each contains Controllers → BusinessLogic → DependencyInjection → ErrorHandling → Models → Program.cs → appsettings.json.
• src/framework: cross-cutting libraries (DBAccess, ErrorHandling, Cors, HttpClientExtensions, Token, Swagger, Logging, Models, DependencyInjection, Seeding, Web, Async).
• src/externalsystems: adapter libraries for external HTTP-based services.
• src/portalbackend: EF Core entities/models and repositories (PortalBackend.DBAccess & PortalBackend.PortalEntities) plus migrations & seeder.
• src/processes: domain process libraries + executors + “Processes.Worker” host.
• src/provisioning: separate DBAccess, library, migrations for provisioning IDP/technical user workflows.
• tests: xUnit projects for each service/library.
• docker: per‐service Dockerfiles and notices.
• GitHub workflows: CI/CD per service and code quality.