> For the complete documentation index, see [llms.txt](https://uci.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://uci.sunbird.org/learn/tech-overview/design-principles.md).

# Design Principles

**Plugin Based -** Adapters, Transformers and Users can all be injected by external providers. Allowing for un-opinionated implementation of specs (which are kept minimal) allowing for simpler, wider and faster adoption.

**Minimal Micro-services -** A simple structure on how the micro-services will interact with each other (specs) and how the information will be stored and processed.

![](https://lh3.googleusercontent.com/OVWuTqk6shpts2Ar2fSX5Hui2_MGH5n2O7J_3JGtUF7LDs8iltWvW-FehjvpMhGE6L9XJkQeFWhThJW5P4KEiMESTIsdtD5Xmz-6fNGlbUCd9lXrBviDfhxa8It2sal-B9P0bhlr)

**Federated Architecture** - We only save configuration as part of the UCI and everything is just called from respective places.

![](https://lh3.googleusercontent.com/IuaVEYpOVGECXdtJlY1Zg46Ub0b9z9aiEXZAmhrcLzWg5zk3NDhZI9zrfOzdIx4kIBhQr6zpztN3mH5I08B5vu-2TrO4K2Jr5QppIebWdel36KQZ58RX1kF0kl2HqqMnQZs_t2nz)

**Data Federation** - All data is secured using JWT and with extreme automation on the building of APIs using data specs.

![](https://lh6.googleusercontent.com/kpq39YFklZIt1EuxVHMwTzRuqoLF5PKTWF8GIJOdo7yDAt5MdWLuGHLUgHXM9FSFrn9jD75kHJ5dS2fzu2QHDBFyzzT6FZM7oPbpMmq8sUbHv2RaVsosGh8_xMooy6W7lBQ5KBCC)

**Population scale** - Asynchronous everywhere with independently scalable small services. Databases that scale horizontally - Cassandra for persistence; Kafka pipeline for decoupling the Saga transactions. Caching at all levels. Deployment auto scalable based on Kafka queue - HPA (k8s).


---

# 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://uci.sunbird.org/learn/tech-overview/design-principles.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.