# Architecture

For developers starting with CARTO, this architecture diagram may help understand how their applications are going to interact with the platform.

<figure><img src="/files/SCXTVqvE4f0FqrzZOX9c" alt=""><figcaption></figcaption></figure>

The most important concepts about the architecture are:

* **CARTO always connects to your data warehouse**: by using live connections to your data warehouse, we can build performant and scalable applications without having to manage complex data migration processes, while respecting your company's governance and security policies.
* **To visualize data in a map you will be using deck.gl:** this visualization library is a requirement. If you're using other visualization libraries at the moment, there are strategies to [combine or overlay](https://deck.gl/docs/get-started/using-with-map) them.

{% hint style="success" %}
**Learn more**

In order to understand what each of these pieces do, the [Libraries and APIs section](/carto-for-developers/key-concepts/apis.md) will cover each component in detail.
{% endhint %}

## JavaScript frameworks

**CARTO is designed to work with any JavaScript-based application**: CARTO will help you accelerate your geospatial development regardless of the framework (eg: React, Vue, Angular...) or stack you're using, as long as your web application uses JavaScript.

## TypeScript support

We recommend using TypeScript when building your apps. You can find more info about this [here](https://deck.gl/docs/get-started/using-with-typescript).


---

# Agent Instructions: 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:

```
GET https://docs.carto.com/carto-for-developers/key-concepts/architecture.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.