> For the complete documentation index, see [llms.txt](https://sitecoreuml.gitbook.io/sitecoredxg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sitecoreuml.gitbook.io/sitecoredxg/architecture/components-overview.md).

# Components

A *component* is a modular program or service that is (primarily) independent of other programs or systems in/on which they are hosted, and satisfies the responsibilities of a SitecoreDXG *role*. By default, a fully-functional SitecoreDXG ecosystem includes the following components:

1. **SitecoreUML Service for Sitecore:** a service endpoint installed on a Sitecore application (PaaS or non-PaaS) as a Sitecore package that satisfies the *serializer* role
2. **SitecoreDXG Middleman:** a program that satisfies the *serializer* role - can be replaced with a own custom middleman implementation, though the **SitecoreDXG RabbitMQ Middleman** is included with SitecoreDXG for rapid setup and use
3. **SitecoreDXG Generation Service:** a node-based service (installable as a Windows service) that initializes and loads the *trigger* and *completion handler* plugins defined in the configuration, and satisfies the *generator* role by performing the generation when called

The following diagram depicts how these components communicate at a high-level:

![](/files/-LMm9Eup3wuWOzy_wnfM)


---

# 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://sitecoreuml.gitbook.io/sitecoredxg/architecture/components-overview.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.