Supported Platforms

Persistence

Parallel execution and high-performance bulk operations for Entity Framework Core.

Free parallel execution and bulk operations on a standard DbContext. Add commercial SQL Server tooling only where transactional, multi-context, or relational composition capabilities are required.

Supported .NET Runtimes

.NET 6 through .NET 10

DataArc packages support application targets across .NET 6 through .NET 10.

Existing and modern .NET applications can adopt DataArc without changing their overall application model.

  • .NET 6
  • .NET 7
  • .NET 8
  • .NET 9
  • .NET 10

Persistence

SQL Server and Entity Framework Core

DataArc.EntityFrameworkCore currently targets SQL Server and works alongside normal Entity Framework Core usage.

Applications continue to use standard Entity Framework Core concepts and APIs, including:

  • DbContext
  • IDbContextFactory<TContext>
  • LINQ queries
  • Change tracking
  • Tracked persistence operations
  • Entity Framework Core transactions
  • Microsoft.Data.SqlClient

DataArc.EntityFrameworkCore adds free high-performance bulk execution where high-volume persistence is required without replacing the normal Entity Framework Core programming model.

Advanced SQL Server capabilities such as transactional bulk execution, multi-context coordination, and relational model composition are available separately through DataArc.EntityFrameworkCore.SqlServer.

.NET Application Models

Web applications, services, workers, and application hosts

DataArc can be used in applications where normal .NET dependency injection and application services are available.

This includes HTTP-facing applications, long-running services, background processing, command-line applications, and desktop-hosted workloads.

  • ASP.NET Core Web API
  • Minimal APIs
  • gRPC services
  • Console applications
  • Worker Services
  • Background Services
  • Windows Services
  • Desktop applications

Hosting Environments

Local, server, container, and cloud deployment

DataArc runs inside the application process and does not require applications to adopt a separate hosting model.

The application retains control of its deployment environment while DataArc provides persistence, orchestration, and observation capabilities where they are required.

  • Local development environments
  • Windows Server
  • Linux hosting
  • Docker containers
  • Cloud-hosted .NET applications

Application Architecture

Introduce DataArc where application boundaries need more structure

DataArc is designed for applications where ordinary .NET and Entity Framework Core patterns remain appropriate but selected application operations require stronger coordination.

DataArc capabilities can be introduced independently according to the requirements of the application.

  • Bulk data processing
  • Transactional persistence workflows
  • Application orchestration
  • Explicit application workflows
  • Modular monoliths
  • CQRS-style applications
  • Integration workflows
  • Multi-DbContext systems
  • Execution observation and application events
  • Relational model composition

Modular Persistence

Keep application boundaries and relational boundaries independent

DataArc supports application architectures where multiple DbContext models represent separate application or domain boundaries.

Those boundaries do not automatically require separate physical databases.

With DataArc.EntityFrameworkCore.SqlServer, multiple independently defined contexts can participate in a deliberately composed relational database topology.

Supported database models can include:

  • Multiple DbContext models in one physical database
  • Schema-based organization
  • Cross-context foreign keys and constraints where appropriate
  • Database-enforced relational integrity
  • Multiple independent relational databases
  • Separate connection strings for independently managed databases

A DbContext boundary does not have to become a relational boundary.

Application Orchestration

Explicit coordination through normal .NET code

DataArc.Orchestrator can coordinate application use-cases across ordinary constructor-injected .NET dependencies.

An orchestrator can coordinate:

  • Application services
  • Persistence operations
  • Multiple DbContext instances
  • Domain policies and operations
  • External services
  • Data transformations
  • Notifications
  • Execution observation

The application execution path remains explicit rather than being hidden behind generic handler chains or dispatch pipelines.

Testing & Validation

Use normal .NET testing and benchmarking tools

DataArc is designed to remain testable through normal .NET test projects and explicit execution boundaries.

Integration tests can validate complete persistence and orchestration workflows, while BenchmarkDotNet can be used to measure performance-sensitive operations such as high-volume bulk execution.

  • NUnit
  • xUnit
  • MSTest
  • Integration testing
  • BenchmarkDotNet

Adopt Only What You Need

Keep ordinary .NET and Entity Framework Core as the foundation

DataArc does not require an application to adopt an entirely new programming or persistence model.

Start with ordinary .NET and Entity Framework Core patterns. Add high-performance bulk execution, application orchestration, or execution observation where those capabilities are useful.

Introduce the commercial DataArc.EntityFrameworkCore.SqlServer capabilities only where transactional execution, multi-context coordination, or relational database composition requires them.