# BrighterCommand/Brighter

A framework for building messaging apps with .NET and C#.

Repository: https://github.com/BrighterCommand/Brighter
Canonical: https://ross.abutalabs.com/products/brighter
Homepage: https://brightercommand.gitbook.io/paramore-brighter-documentation
Language: C#
License: MIT
License Family: permissive
Topics: command-processor, command-dispatcher, brighter, asynchronously, nuget-packages, scale, nuget, rabbitmq, kafka, sqs, sns, redis-stream, dotnet-core, mediatr, csharp-library, csharp, microservices
Last push: 2026-08-26T19:44:03+00:00

## Health v2 (maintenance only)
Score: 98/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 99, release rhythm 95, longevity 100
- inputs: {"age_days": 5719, "days_push": 7, "days_rel": 35, "gap_med": 13, "n_releases_24m": 30}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 2469, forks 293 (observed 2026-08-28T04:06:54.609835+00:00)

## What it is
Brighter is a Command Dispatcher and Command Processor framework for .NET and C# that implements the Command pattern with a middleware pipeline for building loosely coupled applications. It supports both in-process and out-of-process messaging across transports like RabbitMQ, Kafka, AWS SNS+SQS, Redis, and Azure Service Bus, with features such as outbox/inbox patterns, retries, circuit breakers, and distributed tracing.

## Use cases
- build message-driven microservices in .NET
- implement CQRS command side with a command dispatcher
- decouple services with asynchronous messaging over RabbitMQ or Kafka
- add reliable messaging with transactional outbox pattern
- build middleware pipelines for retry and circuit breaking in C#
- process messages from queues with a service activator
- implement hexagonal architecture ports and adapters in .NET

## When to choose
- you are building .NET/C# applications needing command dispatch or event-driven messaging
- you want transport-agnostic messaging with RabbitMQ, Kafka, SQS/SNS, Redis, or Azure Service Bus
- you need outbox/inbox patterns for reliable transactional messaging
- you want middleware-style cross-cutting concerns like logging, retry, and circuit breakers

## When to avoid
- your stack is not .NET (it is a C# library)
- you only need simple in-process request handling without messaging - MediatR alone may suffice
- you need the query side of CQRS without the companion Darker project
- you require a broker or transport not listed among its supported integrations

## Facets
- artifact type: framework
- maturity: active
- function: message-queue, middleware, rpc, workflow-automation, microservices, logging, tracing, error-handling, scheduling
- domain: microservices, backend, developer-tools
- platform: dotnet, cross-platform, cloud
- tags: command-dispatcher, command-processor, cqrs, mediatr-alternative, outbox-pattern, service-activator, hexagonal-architecture, rabbitmq, kafka, aws-sns-sqs, redis-streams, azure-service-bus, event-driven-architecture, messaging, docker

## Member repositories
- BrighterCommand/Brighter (main) score 98

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:06:54.609835+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T02:29:10.103266+00:00, confidence not recorded.
  - readme: https://github.com/BrighterCommand/Brighter (fetched 2026-08-28T04:06:54.609835+00:00, sha 1a7d0a8d50a9)
  - homepage: https://brightercommand.gitbook.io/paramore-brighter-documentation (fetched 2026-08-29T10:10:34.703843+00:00, sha 1acde01b1dc5)
- Data as of 2026-08-30T08:39:29.467469+00:00.