This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-04-01
Channels
- # arachne (3)
- # bangalore-clj (8)
- # beginners (9)
- # cljsrn (3)
- # clojure (148)
- # clojure-filipino (2)
- # clojure-russia (25)
- # clojure-serbia (3)
- # clojure-spec (14)
- # clojure-uk (61)
- # clojureremote (7)
- # clojurescript (38)
- # clojurewest (2)
- # cursive (2)
- # data-science (9)
- # datomic (4)
- # emacs (4)
- # jobs (6)
- # lein-figwheel (3)
- # leiningen (2)
- # off-topic (1)
- # om (3)
- # onyx (1)
- # pedestal (16)
- # perun (2)
- # powderkeg (1)
- # protorepl (2)
- # re-frame (1)
- # reagent (10)
- # spacemacs (2)
- # unrepl (5)
- # untangled (4)
Looks like Pyroclast is built on top of Onyx: http://pyroclast.io/ @anujsays
Good to see Pyroclast going for strong consistency instead of eventual
I recently saw their Clojure/West demo. Really a good one. At the back they are using Datomic and Dynamo DB. Both support strong consistency. Are you referring to the same level?
@anujsays I meant strong consistency as a design choice. Of course, DynamoDB’s offer in read consistency — eventual/strong is quite nice to have. Quite a few systems get built on eventual consistency introducing error-prone complexity in the application dealing with it.
@kumarshantanu saw your message in meetup, I just joined the slack
@robertchristopher Hey! Per the first Saturday convention, the May meetup would be on 6th of May at 3:00pm. Once you confirm the venue (Quintype) I can create the http://meetup.com event.