> For the complete documentation index, see [llms.txt](https://docs.deltastream.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.deltastream.io/overview/core-concepts.md).

# Core Concepts

DeltaStream is a unified analytics platform that combines batch and stream processing and real-time analytics in one platform. Write queries in SQL, and DeltaStream routes them to the optimal execution engine – for example, Flink for streaming, Spark for batch, and ClickHouse for materialized views.

You can also use DeltaStream’s SQL-based interface to build stream processing applications such as streaming pipelines, materialized views, microservices, and more.

{% hint style="info" %}
**Note** DeltaStream sits on top of your streaming data stores, meaning that you should already have one or more streaming stores such as Apache Kafka or AWS Kinesis.
{% endhint %}

This section provides more details on the core concepts in DeltaStream. Below is a brief walk-through of the most important constructs with which to familiarize yourself.

{% @storylane/embed subdomain="deltastream" url="<https://deltastream.storylane.io/share/3tiqde8nosn2>" linkValue="3tiqde8nosn2" %}


---

# 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.deltastream.io/overview/core-concepts.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.