> ## Documentation Index
> Fetch the complete documentation index at: https://clickhouse.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> Documentation for Database Engines

# Database Engines

Database engines allow you to work with tables. By default, ClickHouse uses the [Atomic](/docs/reference/engines/database-engines/atomic) database engine, which provides configurable [table engines](/docs/reference/engines/table-engines/index) and an [SQL dialect](/docs/reference/syntax).

Here is a complete list of available database engines. Follow the links for more details:

| Page | Description |
| - | - |
| [Shared](/docs/reference/engines/database-engines/shared) | Page describing the `Shared` database engine, available in ClickHouse Cloud |
| [Atomic](/docs/reference/engines/database-engines/atomic) | The `Atomic` engine supports non-blocking `DROP TABLE` and `RENAME TABLE` queries, and atomic `EXCHANGE TABLES`queries. The `Atomic` database engine is used by default. |
| [Replicated](/docs/reference/engines/database-engines/replicated) | The engine is based on the Atomic engine. It supports replication of metadata via DDL log being written to ZooKeeper and executed on all of the replicas for a given database. |
| [PostgreSQL](/docs/reference/engines/database-engines/postgresql) | Allows to connect to databases on a remote PostgreSQL server. |
| [MySQL](/docs/reference/engines/database-engines/mysql) | Allows connecting to databases on a remote MySQL server and perform `INSERT` and `SELECT` queries to exchange data between ClickHouse and MySQL. |
| [SQLite](/docs/reference/engines/database-engines/sqlite) | Allows to connect to SQLite databases and perform `INSERT` and `SELECT` queries to exchange data between ClickHouse and SQLite. |
| [MaterializedPostgreSQL](/docs/reference/engines/database-engines/materialized-postgresql) | Creates a ClickHouse database with tables from PostgreSQL database. |
| [Backup](/docs/reference/engines/database-engines/backup) | Allows to instantly attach table/database from backups in read-only mode. |
| [DataLakeCatalog](/docs/reference/engines/database-engines/datalake) | The DataLakeCatalog database engine enables you to connect ClickHouse to external data catalogs and query open table format data |
| [Dictionary](/docs/reference/engines/database-engines/dictionary) | The Dictionary database engine exposes configured dictionaries as read-only tables. |
| [Filesystem](/docs/reference/engines/database-engines/filesystem) | The Filesystem database engine exposes files in a local directory as read-only tables. |
| [HDFS](/docs/reference/engines/database-engines/hdfs) | The HDFS database engine exposes files in HDFS as read-only tables. |
| [Memory](/docs/reference/engines/database-engines/memory) | The Memory database engine keeps database metadata and tables only for the current server session. |
| [Ordinary](/docs/reference/engines/database-engines/ordinary) | The Ordinary database engine is a deprecated legacy engine superseded by Atomic. |
| [S3](/docs/reference/engines/database-engines/s3) | The S3 database engine exposes objects in Amazon S3 and compatible object storage as read-only tables. |
| [URL](/docs/reference/engines/database-engines/url) | The URL database engine exposes URL-addressed data as tables. |