# High-Level Architecture

dSunbird-RC's credentialling service is an amalgamation of three microservices.

* **Identity Microservice:** This service is the central lynchpin to maintain identities across the system. All identities in Sunbird-RC are DID-compliant and are web-resolvable. The other microservices (Credential Schema Service and Credential Service) depend on this for generating any identity.
* **Credential Schema Microservice:** This service stores the schema of the Verifiable Credential along with the associated view template.
* **Credential Issuance Microservice:** This is the core issuance service. This service is called with the payload, which is then transformed into a W3C-compliant Verifiable Credential in JSON-LD format.  The payload is then signed using the private key which was generated as part of the original Issuer creation. 

### High level component Diagram

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

### How it works

The sequence diagram explains the following flows:

* Creating an identity
* Creating a schema
* Issuing a Credential
* Verifying a Credential

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


---

# 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://rc.sunbird.org/learn/technical-overview/credentialling/high-level-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.