> For the complete documentation index, see [llms.txt](https://docs.e6data.com/query-engine/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.e6data.com/query-engine/get-started/architecture/detailed-architecture-walkthrough.md).

# Detailed architecture walkthrough

### A disaggregated SQL engine, built for the open lakehouse

e6data is a distributed SQL query engine that runs directly on your data lake — no ingestion, no proprietary copies, no format lock-in. Your data and catalogs stay inside your boundary; the engine connects to them in place, speaking the protocols your tools already use.

***

**ARCHITECTURE**

#### The architecture

Clients in the customer boundary connect through the protocol layer. The distributed query engine — planners, executors, distribution and metadata services — plans and executes queries, reading data and catalogs that remain in the customer's environment. Each component scales independently.

![e6data architecture diagram](https://256648299-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fz2BYVXehgdnk8dbeZoW5%2Fuploads%2Fgit-blob-9651a9d68da072c0e8d06ac727209004636e3e64%2Fe6-architecture-diagram.png?alt=media)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.e6data.com/query-engine/get-started/architecture/detailed-architecture-walkthrough.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.