# Chromia Database overview · Chromia Docs (concept)

> Understand what makes the Chromia Database unique and when to use it for your application workloads.

Source: https://docs.chromia.com/build/database/overview/

# Chromia Database overview

On this page

* [Why a database-first chain](#why-a-database-first-chain)
* [What to explore next](#what-to-explore-next)

Chromia uses **relational blockchain technology** to give every dapp its own application chain and dedicated data layer.
This section collects the content that helps product teams understand when to reach for the Chromia Database, what it
can do, and how it differs from a traditional L1 or sidechain.

## Why a database-first chain

* Strongly typed data models (via [Rell](https://docs.chromia.com/rell/rell-intro/)) make data-heavy dapps easier to reason about.
* Application chains store data in PostgreSQL, giving you ACID semantics together with the security of the Postchain
  consensus layer.
* Built-in indexing, foreign keys, and JSON/BLOB support make it possible to mix transactional workflows with rich
  content.

## What to explore next

| Topic | Description |
| --- | --- |
| Architecture | Learn how provider nodes replicate state and how state anchoring works. |
| Scaling models | Dive into how horizontal scaling works with multiple application chains. |
| Deployment | Understand how to evolve schemas and roll out migrations. |

Use the sidebar to continue exploring or head to [Getting started](https://docs.chromia.com/build/database/getting-started/) for a practical walkthrough.

[View this page on docs.chromia.com](https://docs.chromia.com/build/database/overview/)Content mirrored from the live docs
