This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-06-22
Channels
- # announcements (8)
- # architecture (1)
- # beginners (49)
- # calva (7)
- # cljdoc (7)
- # cljs-dev (4)
- # clojure (44)
- # clojure-italy (1)
- # clojure-spec (12)
- # clojurescript (88)
- # community-development (2)
- # cursive (8)
- # datomic (16)
- # fulcro (15)
- # immutant (3)
- # joker (10)
- # keechma (4)
- # lambdaisland (1)
- # luminus (7)
- # pathom (1)
- # qa (2)
- # re-frame (11)
- # reitit (8)
- # remote-jobs (1)
- # rewrite-clj (10)
- # shadow-cljs (1)
- # slack-help (2)
- # sql (1)
- # tools-deps (2)
- # vim (4)
- # xtdb (3)
hey guys, quick question suppose I have my application running ( 3 instances ) using datomic peer library. If I push data on application #1 and read data from application #2 , will the read be consistent with the latest data transacted ? ( reading my own write )
There’s possible network propagation delay. A peer will always see a consistent view for a specific t (no half-committed or stale reads), but one peer may know about a TX before another one
Hey @U09R86PA4 thanks ...
@U09R86PA4 how do you usually does on your system to the user read his own writes ? sticky sessions ? ( assuming we are not using peer server )
yeah, I’m returning the new record, but if the user refresh the page could reach a different application instance -> different db -> different attribute value