Documentation

ArturRios.Data is a modular data-access toolkit for .NET. It gives you one consistent, envelope-based repository style across relational databases (EF Core over PostgreSQL / MySQL / SQLite, plus a Dapper read path) and NoSQL stores (MongoDB, DynamoDB), plus file export writers (CSV, JSON, TXT, MessagePack, Excel).

Every read/write operation returns a DataOutput / ProcessOutput envelope, so infrastructure failures — including optimistic-concurrency conflicts — surface as errors on the result rather than as unhandled exceptions.

The package family

Each backend is a separate NuGet package, so you install only what you use. The relational packages share a common core; the NoSQL and export packages are standalone. Everything depends on ArturRios.Output for the envelopes.

flowchart TB
    Output["ArturRios.Output<br/><i>DataOutput / ProcessOutput envelopes</i>"]

    subgraph Relational["Relational stack — EF Core"]
        direction TB
        Core["ArturRios.Data.Relational.Core"]
        Sqlite["ArturRios.Data.Sqlite"]
        Postgres["ArturRios.Data.PostgreSql"]
        MySql["ArturRios.Data.MySql"]
        Dapper["ArturRios.Data.Dapper"]
    end

    subgraph NoSQL["NoSQL stores — standalone"]
        direction TB
        Mongo["ArturRios.Data.MongoDb"]
        Dynamo["ArturRios.Data.DynamoDb"]
    end

    subgraph Export["File export — standalone"]
        direction TB
        ExportCore["ArturRios.Data.Export"]
        ExportExcel["ArturRios.Data.Export.Excel"]
    end

    Sqlite --> Core
    Postgres --> Core
    MySql --> Core
    Dapper --> Core
    Core --> Output
    Mongo --> Output
    Dynamo --> Output
    ExportExcel --> ExportCore
    ExportCore --> Output

Installation

Requires .NET 10.0 or later. Install the package(s) for your backend:

# Relational (EF Core) — the core + a provider matching your engine:
dotnet add package ArturRios.Data.Relational.Core
dotnet add package ArturRios.Data.Sqlite          # or .PostgreSql / .MySql

# Optional raw-SQL read path (relational):
dotnet add package ArturRios.Data.Dapper

# NoSQL (standalone — no core needed):
dotnet add package ArturRios.Data.MongoDb
dotnet add package ArturRios.Data.DynamoDb

# File export (standalone — no core needed):
dotnet add package ArturRios.Data.Export
dotnet add package ArturRios.Data.Export.Excel    # optional — adds ExportFormat.Excel

The result envelope

All operations return a DataOutput<T> (data + success/errors) or, for operations with no payload (deletes, transactions), a ProcessOutput. Inspect Success / Data / Errors instead of catching exceptions.

classDiagram
    class ProcessOutput {
        +bool Success
        +List~string~ Errors
        +List~string~ Messages
    }
    class DataOutput~T~ {
        +T Data
    }
    ProcessOutput <|-- DataOutput

Where to next

• Architecture — package diagram, class diagrams, the envelope model, and the design principles (modular packaging, envelopes-not-exceptions, the provider seam).
• Relational — EF Core setup, provider packages, sync + async repositories, the unit of work, optimistic concurrency, and the Dapper read path.
• MongoDB — document identity, the document repository, server-side Find, the LINQ Query() escape hatch, transactions, and concurrency.
• DynamoDB — item POCOs and keys, the async repository, Query/Scan/batch, and [DynamoDBVersion] concurrency.
• Export — the exporter factory, the CSV/JSON/TXT/MessagePack/Excel formats, the column map and its attributes, and the options.

The source lives at github.com/artur-rios/dotnet-data, licensed under the MIT License.