> For the complete documentation index, see [llms.txt](https://brightercommand.gitbook.io/paramore-brighter-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://brightercommand.gitbook.io/paramore-brighter-documentation/understanding-brighter.md). # Understanding Brighter - [Command, Processor and Dispatcher Patterns](https://brightercommand.gitbook.io/paramore-brighter-documentation/understanding-brighter/commandscommanddispatcherandprocessor.md): The Command design pattern encapsulates a request as an object, allowing reuse, queuing or logging of requests, or undoable operations. - [Using a Task Queue](https://brightercommand.gitbook.io/paramore-brighter-documentation/understanding-brighter/taskqueuepattern.md): The Task Queue Pattern let's you use an External Bus to handle work asynchronously. - [Microservices](https://brightercommand.gitbook.io/paramore-brighter-documentation/understanding-brighter/microservices.md): It is possible to think of microservices as 3rd generation SOA. - [Event Driven Collaboration](https://brightercommand.gitbook.io/paramore-brighter-documentation/understanding-brighter/eventdrivencollaboration.md): Event Driven Architectures (EDA) are a major use case for Brighter's External Bus-you want processes to collaborate via messaging. - [Event Carried State Transfer](https://brightercommand.gitbook.io/paramore-brighter-documentation/understanding-brighter/eventcarriedstatetransfer.md): In his white paper "Data on the Outside vs. Data on the Inside", Pat Helland classifies data according to whether it exists inside a service boundary or outside that boundary. - [Outbox Pattern](https://brightercommand.gitbook.io/paramore-brighter-documentation/understanding-brighter/outboxpattern.md): The Outbox Pattern is what stops a state change and the event announcing it from diverging. - [CQRS with Brighter and Darker](https://brightercommand.gitbook.io/paramore-brighter-documentation/understanding-brighter/cqrswithbrighteranddarker.md): Command Query Responsibility Segregation (CQRS) separates the handling of commands, which change state, from queries, which read it. - [CQRS Use Cases and Patterns](https://brightercommand.gitbook.io/paramore-brighter-documentation/understanding-brighter/cqrswithbrighteranddarker/cqrsusecasesandpatterns.md): Four shapes a CQRS system takes in practice, from a single database with two models to event-sourced writes with projected reads. - [How the Command Processor Works](https://brightercommand.gitbook.io/paramore-brighter-documentation/understanding-brighter/howbrighterworks.md): You don't need to understand how Brighter works under the hood to use it, but if you want to debug, or contribute to the project, it can help to know what is going on. - [How Configuring the Command Processor Works](https://brightercommand.gitbook.io/paramore-brighter-documentation/understanding-brighter/howbrighterworks/howconfiguringthecommandprocessorworks.md): Brighter does not have a dependency on an Inversion Of Control (IoC) framework. - [How the Dispatcher Works](https://brightercommand.gitbook.io/paramore-brighter-documentation/understanding-brighter/howserviceactivatorworks.md): The Dispatcher is the component in the Brighter.ServiceActivator assembly that orchestrates your Performers. - [How Configuring a Dispatcher for an External Bus Works](https://brightercommand.gitbook.io/paramore-brighter-documentation/understanding-brighter/howserviceactivatorworks/howconfiguringthedispatcherworks.md): In order to receive messages from Message Oriented Middleware (MoM) such as RabbitMQ or Kafka you have to configure a Dispatcher. - [Reactor and Proactor: Concurrency Models](https://brightercommand.gitbook.io/paramore-brighter-documentation/understanding-brighter/reactorandproactor.md): Brighter V10 introduces clearer terminology for its concurrency models: Reactor and Proactor. --- # 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://brightercommand.gitbook.io/paramore-brighter-documentation/understanding-brighter.md?ask=&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.