Hi All.
In a recent post Chris Meiklejohn (of Riak KV, Lasp-lang, Partisan, AntidoteDB fame) announced that I will be taking over the maintenance of Partisan off him. See his blog post here 
.
I am hard at work finishing on getting 5.0.0 release ready (currently working on my fork) and merging onto the official repo.
As part of that, I would love to hear from anybody currently using Partisan in their projects so that I can include a link in the upcoming README file.
Version 5.0.0 will bring some API changes so I want to make sure those who are currently using are aware and understand the changes, so any hint on how you are using it that might help me plan a transition and or prioritise documentation topics would be awesome.
Cheers!
12 Likes
Excellent news Alejandro! We are currently using Partisan for our digital twin technology.
We also forked Partisan and tried to keep it up with the new OTP releases. I’ll check out your repo to see if I can propose a contribution with our code.
2 Likes
Fantastic, I’ll post here when finally merging onto the main repo.
2 Likes
@erlangMax I finally merged my fork onto the main repo. Also published a new tag in Hex incl new set of docs using ExDoc.
Check it out at partisan | Hex
7 Likes
Thanks a lot! I’m giving it a run and check if something breaks in our applications.
2 Likes
Cool! I think you will see some breaks due to API changes. In general I am moving most APIs to the partisan module, which implements an API similar (if not identical) to the erlang and net_kernel modules e.g. we now have better monitoring of nodes and remote refs (when using full mesh topology through partisan_pluggable_peer_service_manager
2 Likes