> For the complete documentation index, see [llms.txt](https://knowlg.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowlg.sunbird.org/use/deployment.md).

# Deployment

There are two options to deploy Knowlg:

**Option 1: Independently deploy Knowlg building block**

The necessary documentation for deploying Knowlg independently is currently in the works. You can reach out to us in the community forums and we will assist you to complete the deployment.

<https://github.com/Sunbird-knowlg/Community/discussions>

**Option 2: Deploying Knowlg as part of Sunbird-ED**

Please refer to the [Sunbird-Ed deployment ](https://ed.sunbird.org/use/prerequisites-for-your-own-sunbird-ed-instance)for more details.

{% content-ref url="/spaces/-MkgPDmvKwE\_DgYJbvPS" %}
[Sunbird ED](https://vinukumar-vss-organization.gitbook.io/sunbird-ed/)
{% endcontent-ref %}

![](https://1767651289-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaanfWbeVT74C5lXDPde3%2Fuploads%2FvdungRkK7eRkP1QtytZm%2FSB-Knowlg%20\(2\).png?alt=media\&token=3c108367-964d-4a4a-92cc-a41c9bd07600)

[SB-Knowlg ](https://knowlg.sunbird.org/)is packaged with some micro-services as shown in the above architecture.

* [Content-service](/learn/product-and-developer-guide/content-service.md)
* [Search-service](/learn/product-and-developer-guide/assets-search-service.md)(also called asset-search-service)
* [Taxonomy-service](/learn/product-and-developer-guide/taxonomy-and-tagging.md)
* [DIAL-service](/use/installation-guide/services/dial-service.md)

The below list of DB's are used in the above micro-services

* **Neo4J**: \
  This is used as a primary data store of the content-service & Taxonomy-service. The data of each asset is stored as a graph node. The data from this Neo4j DB will sync to Elasticsearch through flinkJob(search-Indxer) for ease of discovery.
* **Cassandra:**\
  This DB is used by content-service, Taxonomy-service & DIAL service. \
  *Content-service:* The asset data is stored in Neo4J. B the external/additional data of the asset will be stored in Cassandra because of large size data/information like Body, Collection hierarchy etc.\
  *Taxonomy-service*: Object category definations are stored here. \
  DIAL-service: We are using Cassadra as a primary store of DIAL data/information. This data will be synced to Elasticsearch through flinkJob(search-Indxer)
* **Redis:**\
  To improve the performance of API instead of hitting the DB for every Read call, we are using the Redis as temp cache.
* **Elasticsearch:**\
  This is the primary DB of the search-service(asset-search-service). There is not directly feed/post of the data to the elastic-search DB. The data will be synced from Neo4J to elasticsearch through Flink job(Search-indexer) only.<br>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowlg.sunbird.org/use/deployment.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.