You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
`HordePro` is a Postgres-backed distributed supervisor and registry.
4
+
`Horde` is a distributed Supervisor and Registry.
5
5
6
-
HordePro shares no code with Horde and has been completely re-written from the ground up, using what I learned from Horde and the better part of a decade in hindsight.
6
+
This version of Horde reflects years of practical experience with Elixir and distributed systems. It introduces a refined architecture focused on stability, maintainability, and ease of operation, while keeping the API familiar to existing users.
7
7
8
-
HordePro is backed by Postgres rather than the CRDT library that Horde uses (also written by me). I think this is a better choice for most users, since Postgres is already a singleton in most stacks, and this allows me to simplify things considerably. As such, HordePro should be more stable and easier to maintain and extend.
8
+
One of the key design choices is the use of Postgres as the coordination back-end. Since Postgres is already a reliable singleton component in most stacks, this allows Horde to simplify its internal design and offer more predictable operational behavior.
9
9
10
-
HordePro remains 99% API-compatible with `Elixir.DynamicSupervisor` and `Elixir.Registry`, and improves upon the API coverage offered in Horde.
10
+
Horde remains 99% API-compatible with `Elixir.DynamicSupervisor` and `Elixir.Registry`, and improves upon the API coverage offered in Horde.
11
11
12
-
Currently HordePro only supports Postgres as a back-end. If you are interested in running it against MariaDB or something else, please get in touch with me.
12
+
At the moment, Horde supports Postgres as its back-end. If you are interested in using other databases, such as MariaDB, feel free to reach out.
13
13
14
-
See `HordePro.DynamicSupervisor` and `HordePro.Registry` for documentation.
15
-
16
-
## Getting Started
17
-
18
-
Purchase a subscription to HordePro at Code Code Ship.
14
+
Refer to `Horde.DynamicSupervisor` and `Horde.Registry` for detailed documentation.
19
15
20
16
## Installation
21
17
22
18
If [available in Hex](https://hex.pm/docs/publish), the package can be installed
23
-
by adding `horde_pro` to your list of dependencies in `mix.exs`:
19
+
by adding `horde` to your list of dependencies in `mix.exs`:
24
20
25
21
```elixir
26
22
defdepsdo
27
23
[
28
-
{:horde_pro, "~> 0.1.0"}
24
+
{:horde, "~> 0.1.0"}
29
25
]
30
26
end
31
27
```
32
28
33
29
Documentation can be generated with [ExDoc](https://github.com/elixir-lang/ex_doc)
34
30
and published on [HexDocs](https://hexdocs.pm). Once published, the docs can
Copy file name to clipboardExpand all lines: TODOS.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,5 +21,5 @@
21
21
- use LISTEN / NOTIFY instead of polling in *Manager
22
22
23
23
## Considering
24
-
-HordePro.Supervisor
24
+
-Horde.Supervisor
25
25
- I have seen this being requested a number of times. Sometimes people want to start a static list of processes and have them be uniformly distributed across their cluster. Perhaps we can meet this use case.
0 commit comments