database-repository

A repository pattern for JSON storage uses a DataContext with IQueryable properties and a PersistenceSession to handle transactional changes. It provides a generic IRepository for CRUD operations on domain entities.

The unit-of-work pattern for JSON data contexts is implemented via a PersistenceSession. You open a session, attach or delete entities, then call SubmitChanges to transactionally persist all modifications to the JSON storage.

Yes, JSON-backed repositories support computed columns specifically for fast querying. The DataContext provides a CreateQuery entry point allowing you to run queries against computed columns and aggregate domain entities efficiently.

No external database or ORM framework is required. The repository pattern operates entirely on JSON-based storage with an Entity base class containing WebId and audit fields, handling data access boilerplate without external dependencies.

The best way to structure CRUD operations for JSON-stored entities is using a generic IRepository pattern. It enables loading, saving, updating, and deleting domain entities through a controlled workflow managed by the DataContext and PersistenceSession.

You should avoid a JSON file repository pattern in applications requiring high concurrency, large-scale relational data, or complex transactional integrity across multiple data sources, as JSON storage is optimized for simpler domain entity persistence.