commanded/commanded

Health v2 · maintenance only

Adoption not part of the score

2030 stars · 256 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

Commanded is an Elixir framework for building applications using the CQRS (Command Query Responsibility Segregation) and Event Sourcing (ES) patterns. It provides command registration and dispatch, aggregate hosting, event handling, and long-running process managers, with pluggable event store persistence.

Use cases

• build a CQRS application in Elixir
• implement event sourcing with aggregates
• dispatch and route commands to domain aggregates
• create long-running process managers
• persist events to an event store backed by Postgres
• model a complex domain with event-driven architecture
• handle events asynchronously in a distributed system

When to choose

• You are building an Elixir application and want to follow the CQRS/ES pattern
• You need a solid, battle-tested foundation for command dispatch, aggregates, and event handling
• You want to focus on domain modelling rather than infrastructure plumbing
• You need pluggable event store persistence (e.g., Postgres-backed EventStore)

When to avoid

• You are not using Elixir or the BEAM ecosystem
• Your application is simple CRUD and does not benefit from CQRS/ES complexity
• You need a turnkey application rather than a framework to build on
• You require an event store other than the supported options without custom integration work

Facets

framework · maturity stable

middleware message-queue workflow-automation serialization database-driver backend developer-tools microservices apis elixir jvm windows cross-platform self-hosted cqrs event-sourcing elixir eventstore aggregates process-managers command-dispatch domain-driven-design hex-package postgres automation linux macos web-server

Member repositories

For agents

markdown · JSON · MCP: product_card(name="commanded/commanded")