> For the complete documentation index, see [llms.txt](https://docs.rumi.systems/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rumi.systems/rumi-core/concepts/microservice-architecture.md).

# Microservice Architecture

The diagram above illustrates the Rumi microservice architecture.

* Below the dashed line constitute the Rumi runtime of a microservice.
* Above the dashed line are user developed artifacts and code

This section contains the following subsections:

* [Runtime Architecture](/rumi-core/concepts/microservice-architecture/runtime-architecture.md) provides a high level description of the components that comprise the Rumi microservice runtime.
* [Development Model](/rumi-core/concepts/microservice-architecture/development-model.md) describes the the various artifacts a developers works with and the role that the Application Data Modeler (ADM) plays in the development process.
* [Configuration Model](/rumi-core/concepts/microservice-architecture/configuration-model.md) provides a high level overview of the architecture of the Rumi configuration subsystem and the artifacts used by a developer to populate the configuration repository - the repository from where the Rumi runtime components source their configuration.


---

# 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.rumi.systems/rumi-core/concepts/microservice-architecture.md?ask=<question>&goal=<endgoal>
```

`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.