---
title: Cratis Arc Entity Framework Core integration
editUrl: https://github.com/Cratis/Arc/edit/main/Documentation/backend/csharp/entity-framework/index.md
description: Use Entity Framework Core with Cratis Arc for relational persistence, query-oriented contexts, JSON conversion, and observed query results.
lastUpdated: 2026-11-05T00:00:00.000Z
---


Cratis Arc's Entity Framework Core integration lets your application store and query relational data without requiring Chronicle or event sourcing. Add the optional `Cratis.Arc.EntityFrameworkCore` package when you need relational persistence, then follow [getting started](/arc/backend/csharp/entity-framework/getting-started/) to register your contexts and select a provider. Apply your database schema separately; registration does not create it.

## Topics

| Topic | Description |
| --- | --- |
| [Getting Started](/arc/backend/csharp/entity-framework/getting-started/) | How to configure Entity Framework Core with Arc, including auto-discovery and observation support. |
| [Base DbContext](/arc/backend/csharp/entity-framework/base-db-context/) | Apply Arc's model conventions to your context. |
| [Entity Mapping](/arc/backend/csharp/entity-framework/entity-mapping/) | Keep entity configuration in IEntityTypeConfiguration&lt;T&gt; classes. |
| [Read Only DbContexts](/arc/backend/csharp/entity-framework/read-only/) | How to implement read-only database contexts for query scenarios. |
| [Automatic Database hookup](/arc/backend/csharp/entity-framework/automatic-database-hookup/) | Provider detection, pooled context registration, and connection-string limits. |
| [Upserts](/arc/backend/csharp/entity-framework/upserts/) | Tracked persistence and atomic native upserts for SQL Server, PostgreSQL, and SQLite. |
| [Observing DbSet](/arc/backend/csharp/entity-framework/observing/) | Refresh query results after changes, with provider-specific notification setup and explicit lifetime ownership. |
| [Common Column Types](/arc/backend/csharp/entity-framework/common-column-types/) | Common column type configurations and conventions. |
| [Property Extensions](/arc/backend/csharp/entity-framework/property-extensions/) | Configure value conversion for individual properties. |
| [Json](/arc/backend/csharp/entity-framework/json/) | Store marked properties as JSON with provider-specific column types and configurable serialization. |
| [Geometry storage paths](/arc/backend/csharp/entity-framework/point-conversion/) | Explicit string conversion versus JSON properties and spatial migration declarations. |
| [Guid conversion](/arc/backend/csharp/entity-framework/guid-conversion/) | SQLite string conversion and migration type differences. |
| [Concept conversion](/arc/backend/csharp/entity-framework/concept-as-conversion/) | Store strongly typed values. |

## Overview

Choose a context around the work it performs. Use [BaseDbContext](/arc/backend/csharp/entity-framework/base-db-context/) for Arc's model conventions, or combine [read-only contexts and registration](/arc/backend/csharp/entity-framework/read-only/) for query code with no-tracking reads and SaveChanges guards. Database permissions remain the boundary when writes must be prevented.

For complex properties, choose [JSON conversion](/arc/backend/csharp/entity-framework/json/) or an explicit [geometry storage path](/arc/backend/csharp/entity-framework/point-conversion/) before creating migrations: a JSON string converter is not a native spatial mapping. Once ordinary reads work, [observe a DbSet](/arc/backend/csharp/entity-framework/observing/) if clients need refreshed results. That page explains which writes each provider can detect and how to own the observation's lifetime.
