> For the complete documentation index, see [llms.txt](https://docs.dat-hub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dat-hub.com/overview/core-concepts/destination.md). # Destination The destination is the place where the transformed data is loaded after extraction and transformation. For loading high dimensional vector embeddings we require vector databases as the final destinations. Some examples of vector databases are Pinecone, Weaviate, Qdrant, Milvus etc. The destination is a crucial element of the data ETL process as it marks the final stage where the data, after going through various stages of cleaning and conversion to embeddings, is deposited for use in analytics or other business processes. Ensuring that the data is correctly loaded into the destination system is vital for maintaining data integrity and enabling accurate insights. When choosing an appropriate destination you must bear in mind the performance, scalability, compatibility with existing tools and software, cost etc. For example, if moving data from a Postgres database, into a Qdrant vector database, then Qdrant is the destination. --- # 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.dat-hub.com/overview/core-concepts/destination.md?ask=&goal= ``` `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.