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

# Reference guide

- [Configuration and boostrapping](https://docs.revoframework.net/reference-guide/configuration.md): Prior to bootstrapping a Revo application, one must first set up the framework and specify its configuration, which makes it possible to customize its behavior in a number of ways.
- [Dependency injection](https://docs.revoframework.net/reference-guide/dependency-injection.md): Like many other frameworks, Revo also builds on the principles inversion of control (IoC). For the heavy lifting, the framework uses the open-source Ninject dependency container and injector.
- [Domain building blocks](https://docs.revoframework.net/reference-guide/domain-building-blocks.md)
- [Commands and queries](https://docs.revoframework.net/reference-guide/commands-and-queries.md): The framework implements a number of facilities for working with commands, queries and for implementing CQRS.
- [Events](https://docs.revoframework.net/reference-guide/events.md): Events are one of the most powerful ways of communication used in Revo. The framework offers a few different ways for implementing an event-driven architecture.
- [Data persistence](https://docs.revoframework.net/reference-guide/data-persistence.md)
- [Database migrations](https://docs.revoframework.net/reference-guide/database-migrations.md): Database migrations in Revo are a simple feature how to version database schema.
- [Projections](https://docs.revoframework.net/reference-guide/projections.md): Projection are specialized event listeners used for materializing events published by event sourced aggregates into better usable read models.
- [Authorization](https://docs.revoframework.net/reference-guide/authorization.md)
- [Validation](https://docs.revoframework.net/reference-guide/validation.md)
- [Request life-cycle](https://docs.revoframework.net/reference-guide/request-life-cycle.md)
- [Sagas](https://docs.revoframework.net/reference-guide/sagas.md)
- [Jobs](https://docs.revoframework.net/reference-guide/jobs.md)
- [Messaging and integrations](https://docs.revoframework.net/reference-guide/integrations.md): Scale and integrate by publishing and receiving events, commands and queries using common messaging patterns, e.g. with RabbitMQ message queue (using EasyNetQ connector or Rebus service bus).
- [Multi-tenancy](https://docs.revoframework.net/reference-guide/multi-tenancy.md)
- [Testing](https://docs.revoframework.net/reference-guide/testing.md)


---

# 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.revoframework.net/reference-guide.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.