To understand how the backend fits into the broader system, we recommend reviewing the following resources:

*[General Concepts](../admin/infrastructure/validated-architectures/index.md#general-concepts): Essential concepts and language used to describe how Coder is structured and operated.

*[General Concepts](../../admin/infrastructure/validated-architectures/index.md#general-concepts): Essential concepts and language used to describe how Coder is structured and operated.

*[Architecture](../admin/infrastructure/architecture.md): A high-level overview of the infrastructure layout, key services, and how components interact.

*[Architecture](../../admin/infrastructure/architecture.md): A high-level overview of the infrastructure layout, key services, and how components interact.

These sections provide the necessary context for navigating and contributing to the backend effectively.

break existing Coder deployments:

* Partial fixtures

* Full database dumps

Both types behave like database migrations (they also

[`migrate`](https://github.com/golang-migrate/migrate)). Their behavior mirrors

Then add some queries to insert data and commit the file to the repo. See

for an example.

To create a full dump, run a fully fledged Coder deployment and use it to