FYI,
There have been several updates on github for this library recently by the author.
Not sure why he isn’t posting them here as they are useful!
Shifters
shifters98
anuaralfetahe
I’m pleased to know that there’s interest in the development progress. I’ll continue to update any future releases here.
I’d like to share some plans regarding the library. One of the primary upcoming goals is to optimize the library by identifying bottlenecks and areas where improvements can be made. The most recent release introduced configurable timeouts, which are essential for larger systems with a significant number of nodes and processes, and which can tolerate higher latencies. This enhancement has also laid the groundwork for performance testing and fine-tuning. I’ll update the documentation later by including general guidelines for configuring timeouts and other parameters based on the cluster size and the number of processes.
Additionally, I’ll need to expand the documentation and provide more guides because various configurations and methods are undiscovered in the current documentation.
Prior to optimizing and improving the documentation, I’ll enhance the hook system to make it more robust. This will provide additional ways to extend or modify the system’s behavior. At this point, it should be relatively straightforward to replace built-in strategies with custom implementations that can hook into the system at different points as needed and execute code.
Hopefully 0.x.x-beta soon 
3
shifters98
nulltree
Yes, while I don’t have any immediate use cases for this, I’m kind of silently following along since your first post as the topic deeply fascinates me.
Thanks for the docs especially, I am learning a thing or two from them!
1
anuaralfetahe
New Release 0.2.4-alpha
This release focuses on the hook system. The new hook system includes:
- New hooks
- Struct-based hook handlers
- Hook handler priorities
- New functions in the
ProcessHub.Service.HookManagermodule to register and remove hook handlers
The base behaviors for different strategies have also been simplified by removing many callback functions. These callbacks are now dynamically attached to the running system using hooks. This means we only need to implement the callbacks that are truly necessary, primarily pure functions where a return value is expected.
Additionally, this enhancement allows us to extend the system further by hooking into different parts of it.
Happy coding!
1
shifters98
slouchpie
I started exploring this library a few hours ago and it is extremely good. I have used horde in the past and pogo more recently. Both of those libs are great but process_hub is truly a joy to use.
There is a lot to love and I have not even started using the hot-swapping and hooks stuff. Reading the list of hook events blew my mind. My imagination was piqued.
I love the simplicity of the hub_id atom. This plays well with Fly because the fly region can be used to build the hub_id, for simple per-region clustering.
I also love the way you use local ETS tables for fast lookup. Perfect use-case for ets.
I am still doing a refactor on a feature branch to see if my own hacky :pogo-based attempts at distributed process management can be replaced with :process_hub. So far I refactored a cache for oauth “state” and a per-kitchen “global singleton” order number generator process. I have way less LOC already and it is far simpler to read and understand.
I am in awe. Congratulations.
5
anuaralfetahe
Hi,
Thank you for the feedback!
In the next release, I will improve the documentation to make it easier for others to use the library. Additionally, I plan to stress test the library with different configuration combinations and post the results. This will be helpful later when deciding on values for timeouts and other settings.
I will keep you all posted on the progress.
I also noticed an error in the documentation regarding hooks. The example for dynamic hook registration using the ProcessHub.t/0 configuration struct was still showing the deprecated method for defining hook handlers.
The correct method uses the new HookManager struct, as shown below:
%HookManager{
id: :hook_id_1,
m: MyModule,
f: :my_function,
a: [:some_data, :_]
}
I will review the documentation and upload the corrections.
The library is still in the alpha stage, so there are likely some issues. If you find any problems, please report them on GitHub or in this forum, and I will gladly fix them all.
Thank you again for the awesome feedback!
2
slouchpie
I think I found a bug when trying to stop a child that has a string ID.
3
