Clojurians Log v2

my apologies, it's public now.

I'll need (to buils) one soon

I've been thinking about something similar from another angle, but this also relates to distribution of work and state persistence. If we can distribute work between client and server, how can we distribute work among servers in a similar manner? I want (via remote ...)

what I've done in the past (without missionary) is have the servers pick up tasks when they have capacity. For that I have a job table in postgres, and use a skip lock in a transaction to process the task:

(postgres/execute-one! postgres
                               {:delete-from :scheduled-tasks
                                :where [:=
                                        :id
                                        {:select :id
                                         :from [:scheduled-tasks]
                                         :order-by [:execute-at]
                                         :where [:<= :execute-at now]
                                         :for [:update :skip-locked]
                                         :limit 1}]
                                :returning [:*]})

I would just use https://github.com/manetu/temporal-clojure-sdk

I started working on something like that. I didn't quite get it to a usable state for lack of time or focus, but you can look at it if you are interested https://github.com/AdamFrey/missionary-pipelines

Link 404s

@adamfrey seems like a private repo