Jebi.SDK.Rest 1.0.1

Jebi

Jebi is a .NET library that maps JSON data onto a relational database, applying configurable transformation rules to bridge structural differences between source JSON and the target EF Core model.

Architecture

Jebi is split into two distinct layers:

Server (hosted service)

A single combined REST server exposes both the Catalog and Ingestion Plan surfaces:

Endpoints:

• api/source/* — JSON schema management
• api/target/* — EF Core DbContext metadata
• api/bindings/* — binding configurations and transformation rules
• api/plan/* — ingestion plan setup and key correlations

Client (NuGet package)

How It Works

Consumer App
  └── IJebiSdkService          (from Jebi.SDK.Rest package)
        ├── Catalog calls  ──→ HTTP  → Jebi Server (api/source, api/target, api/bindings)
        ├── Plan calls     ──→ HTTP  → Jebi Server (api/plan)
        └── Execute        ──→ local → JebiIngestionDb + consumer's target DbContext(s)

The server holds all metadata (schemas, target models, binding rules, plans). Execution runs client-side against the consumer's own databases.

Infrastructure Projects

The server requires two connection strings:

"ConnectionStrings": {
  "JebiCatalogDb": "...",
  "JebiPlanDb": "..."
}

SDK Registration

REST (production)

builder.Services.AddJebiSdkRest(
    serverBaseAddress: "https://jebi.example.com",
    jebiIngestionConnectionString: "Data Source=jebi-execute.db",
    tenantRemoteTokenOptions: tenantOptions,
    ensureTargetDatabases: true,
    typeof(MyTargetDbContext));

Local (development / testing)

builder.Services.AddJebiSdkLocal(
    jebiCatalogConnectionString: "Data Source=catalog.db",
    jebiIngestionConnectionString: "Data Source=plan.db",
    ensureTargetDatabases: true,
    typeof(MyTargetDbContext));

Facade Usage

var jebi = serviceProvider.GetRequiredService<IJebiSdkService>();

var binding = await jebi.CreateBindingConfigurationAsync(new JebiCreateBindingConfigurationRequestDto
{
    SourceSchemaName = "CustomerSchema",
    TargetContextName = "MyTargetDbContext",
    Name = "CustomerBinding"
});

await jebi.AddPropertyBindingRuleAsync(new JebiAddPropertyBindingRuleRequestDto
{
    BindingConfigurationId = binding.BindingConfigurationId,
    SourcePropertyName = "CustomerDef.customerId",
    TargetPropertyFullyQualifiedName = "MyApp.Customer.CustomerId"
});

var result = await jebi.RunFromBindingAsync(new JebiRunFromBindingRequestDto
{
    BindingConfigurationName = "CustomerBinding",
    JsonPayload = jsonPayload,
    Options = new JebiIngestionOptionsDto { ValidateSchema = true, PersistRequested = true }
});

Solution Filters

Work on a focused subset of the solution using the available filters:

dotnet build Jebi.Catalog.slnf
dotnet build Jebi.Ingestion.slnf
dotnet build Jebi.SDK.slnf
dotnet build Jebi.AppHost.slnf

Architecture Boundaries

Check project boundary rules:

bash scripts/ci/check-project-boundaries.sh

Validates that:

• consumer apps have DisableTransitiveProjectReferences=true
• SDK surface packages do not expose internal projects as compile dependencies

Also enforced in CI via the Architecture Boundaries workflow.

Docker

Pull and run the server:

docker pull ghcr.io/boffoli/jebi-catalog-ingestionplan-server-rest:latest
docker run -d -p 8080:8080 ghcr.io/boffoli/jebi-catalog-ingestionplan-server-rest:latest

See docs/docker-demo-launchers.md for ready-to-use launcher scripts.