Learn Ark Data Layer

Ark Data Layer supplies mechanics for concrete Repository implementations. It does not move persistence concerns into the domain or turn DataSourceContainer into an application-wide service locator.

Recommended path

1. Getting started builds one small but complete Repository.
2. Architecture and boundaries assigns responsibilities to Domain, Data, Application, and Composition layers.
3. DataSource contracts explains narrow technical contracts and strict resolution.
4. Repository and domain interfaces separates the reusable base from the business-facing abstraction.
5. Observable data and lifecycle defines replay, ordering, closing, and ownership.

Continue with a tutorial when you need a complete project flow, or open Recipes for one focused operation.