> For the complete documentation index, see [llms.txt](https://docs.rierino.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rierino.com/devops/microservices.md).

# Microservices

Typical microservice development with Rierino follows 3 main steps, building and using reusable components in each step:

1. Configuration of micro-composable [elements](/devops/microservices/building-blocks.md), which define data stores and streams to use, key functions to execute and systems to access. These elements are configured once and utilized by multiple runners, minimizing workload and user errors, while making it possible to create infinite number of runners with plug and play capabilities.
2. Assembly of [runners](/devops/microservices/service-runners.md), which is basically defining list of micro-composable elements to include inside a runner, and defining relations between them (such as which handler to respond to which type of requests coming from a stream). A runner itself does not mandate how it is deployed (e.g. which cloud provider, which containerization), isolating deployment from design.
3. Structuring of [deployments](/devops/microservices/deployment-packages.md), which describes how and where to deploy each runner, including required CD settings. Typically, a deployment is executed by triggering a specific Jenkins or similar automation task with specific parameters. A deployment can include one or more runners, which allows for shrinkage or expansion of scale.

{% embed url="<https://www.youtube.com/watch?v=qIJNBnN6v8U>" %}


---

# 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.rierino.com/devops/microservices.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.