commanded
todo_backend_commanded
Our great sponsors
| commanded | todo_backend_commanded | |
|---|---|---|
| 4 | 2 | |
| 1,791 | 10 | |
| 1.3% | - | |
| 7.9 | 10.0 | |
| 2 months ago | almost 2 years ago | |
| Elixir | Elixir | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
commanded
-
Show HN: Light implementation of Event Sourcing using PostgreSQL as event store
This reminds me of Commanded[0] for elixir which also uses Postgresql by default.
[0]https://github.com/commanded/commanded
-
Adding soft delete to a Phoenix Commanded (CQRS) API
So, I lied told a half-truth about aggregates. They are not hydrated in-memory for every command / event. In reality, aggregates are implemented with GenServer each caching their state and being managed under the commanded application's supervision tree (ultimately by a DynamicSupervisor called Commanded.Aggregates.Supervisor, to be specific).
-
Using CQRS in a simple Phoenix API with Commanded
The Commanded hex package is a fabulous CQRS library used by some real companies in production, but it doesn't have a great on-ramp.
-
Phoenix LiveView, but event-sourced
The context: I'm building a cryptocurrency exchange application. I don't have the business chops to run an actual exchange, so this is just for fun. The application is built in Elixir, using the Commanded framework for CQRS/ES goodness, and Phoenix LiveView because it's the hot new thing that I wanted to learn.
todo_backend_commanded
-
Adding soft delete to a Phoenix Commanded (CQRS) API
(Link to relevant commit)
-
Using CQRS in a simple Phoenix API with Commanded
Follow along with what I learned while implementing a project named todo_backend_commanded. Its git history reflects the process of migrating from a vanilla Phoenix API to an event sourced solution.
What are some alternatives?
ex_admin - ExAdmin is an auto administration package for Elixir and the Phoenix Framework
graphql_parser - Elixir binding for libgraphqlparser
plug - Compose web applications with functions
plug_cloudflare - Parses CloudFlare's CF-Connecting-IP header into Plug.Conn's remote_ip field.
phoenix_live_reload - Provides live-reload functionality for Phoenix
torch - A rapid admin generator for Elixir & Phoenix
phoenix_ecto - Phoenix and Ecto integration with support for concurrent acceptance testing
ashes - A code generation tool for the Phoenix web framework
phoenix_haml - Phoenix Template Engine for Haml
Raxx - Interface for HTTP webservers, frameworks and clients
blaguth - Basic Access Authentication in Plug applications
absinthe_plug - Plug support for Absinthe, the GraphQL toolkit for Elixir