Deon, This is outstanding. I experimented with a similar approach last summer, but struggled with a couple of things. First was what to use for the event store. I considered a few options, like using Datomic for that as well (I.e. annotate transactions and treat the sequence of transactions as the event stream) and even just using Kafka and retaining the logs indefinitely. Both of those options have problems. I like your approach of using a simple KV store - I'm embarrassed that I didn't think of that earlier.
Probably the biggest issue was the overall glue to tie the system together in an extensible way. This was before Onyx was released, and although when I saw Onyx I thought it was promising, I had moved on to a different project and didn't have the time look into it fully. I'm glad to see someone else has done that work. I think this approach is very promising, and I will be digging into your system at the first opportunity. Thank you so much for sharing this work with the community. Mike -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
