@gardnervickers: That would explain why they feel similar! I have a hard time moving past the jargon at this stage and seeing the underlying similarities between different distributed computational systems.

@drewverlee: Yea, its not immediately apparent.

@robert-stuttaford: Still in the process of adding more to the API and cleaning everything up, but I believe this should be useful for your immediate needs: https://github.com/onyx-platform/lib-onyx#log-subscription

& the section below it

@lsnape: Sorry that it took a little longer than expected. I uploaded a new Docker image with a preloaded Onyx log. docker pull michaeldrogalis/onyx-log:0.1.1 will bring it down. This time I removed the ZooKeeper volume, so it should be entirely self contained.

thanks michaeldrogalis ! i’ll check it out

ready when you are, @lucasbradstreet

actually, @greywolve will cover this investigation with you – my day has filled up!

@greywolve @robert-stuttaford no worries, I can start in a little bit

@michaeldrogalis: nice thanks!

I’ve spent a couple of hours bootstrapping the project: https://github.com/lsnape/onyx-log-ui Not much to see yet. Mostly been swapping out Jetty for Aleph & Compojure for Bidi/Yada 😄 I’ve component-inated the log client and seems to be working. Next step is to setup the frontend. Might find some time for that tomorrow

@lsnape: I have been super interested in yada, was sort of hoping to see that used with the log reader haha. Very cool!

I like me some bidi

@gardnervickers: it’s great to have the HTTP compliance out of the box. Reason why I spent time swapping it out though is that it looks easy to setup with an Om Next remote

should be able to use SSE for the log messages

Nice, it’ll be great if we can have a plug ’n play om.next query parser

for the log

I got the idea from this article: https://blog.juxt.pro/posts/course-notes-2.html

if you scroll to the bottom of the article you’ll find some implementation details for a yada event stream resource

Cool thanks

Great work, thanks @lsnape 😄

Looks v cool

@lsnape: For what its worth, we're standing up some generic query service for the log. It might overlap a smidge with what you're doing - just a heads up. We need it elsewhere for a specific context.

Muuuuch smaller scope on that one

Its still in flux though, just wanted to give you a heads up incase you found it.

Right, what he said