Hacker News Reader

Ash models an application's verbs or operations as actions. This allows the production of events via an "Aspect Oriented" way of hooking into the action lifecycle.

Although it doesn't support a command first Event sourcing approach, AshEvents (https://github.com/ash-project/ash_events) does help produce events that could be replayed.

Torkild wrote an article about his latest updates to AshEvents here:

https://alembic.com.au/blog/ash-events-event-sourcing-made-s...

The GraphQL layer is built on top of Absinthe. If you really find something you can't model with Ash's actions, you can always just jump to your Absinthe schema and write you own queries/mutations/subscriptions. You'll just need to write your own resolver.

AshCommanded: A declarative CQRS / ES extension for Ash

https://elixirforum.com/t/ashcommanded-a-declarative-cqrs-es...

https://github.com/accountex-org/ash_commanded

AshGraphQL (https://github.com/ash-project/ash_graphql) errors are relatively customisable

https://hexdocs.pm/ash_graphql/handle-errors.html