ARKTELOS / PRODUCTS / ARK DATA LAYER

Explicit data boundaries with observable business state.

Ark Data Layer provides pure-Dart foundations for repositories, typed DataSources, and current business-data publication without coupling the domain to storage or a framework.

Read the documentationpub.dev ↗Source ↗
Multiple DataSources pass through one stable typed boundary and resolve into a domain output.DATASOURCEDATASOURCEDATASOURCETYPED BOUNDARYREPOSITORYDOMAIN
Multiple DataSources pass through one stable typed boundary and resolve into a domain output.

FIT / EVALUATION

Confirm the boundary before adopting the package.

Platform
Pure Dart
Primary package
ark_data_layer
Current release
1.1.0
Responsibility
Defines typed DataSource and Repository boundaries and publishes current business data through a domain-owned contract.
Use when
Use it when technical data sources must remain behind a stable Repository while application code observes business data.
Does not own
It does not prescribe storage clients, schedule application work, or own presentation and routing.

Shortest evaluation path

  1. 01

    Confirm the responsibility and deliberate boundary above.

  2. 02Open tutorials →
  3. 03

    Inspect package ↗Inspect source ↗

01 / MODEL

Technical sources converge into a domain Repository.

DataSources describe narrow technical contracts. A DataSourceContainer exposes them to one Repository implementation. The Repository maps technical models, retains current business data, and publishes every committed change.

Three technical DataSources reach a Repository through a typed container. The Repository publishes domain data to observers.REMOTELOCALMEMORYDATASOURCE CONTAINERTYPEDLOOKUPREPOSITORYDOMAINDATAOBSERVERS
  1. DataSource
  2. DataSourceContainer
  3. Repository
  4. Domain data
Three technical DataSources reach a Repository through a typed container. The Repository publishes domain data to observers.

02 / BOUNDARIES

The package keeps architectural boundaries visible.

01

Domain

Declares a Repository interface in business language and knows nothing about DataSourceContainer, DTOs, or storage clients.

02

Data

Implements the Repository, coordinates DataSources, and maps technical models into domain data.

03

Application

Observes the domain interface and, when needed, connects changes to a UseCase through a regular Command.

03 / DOCUMENTATION

Choose a learning path.

Start with architectural boundaries, build a complete data layer in a tutorial, or open a concise recipe for one task.

Learn→Tutorials→Recipes→Packages→Releases→