This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-03-31
Channels
- # announcements (16)
- # beginners (52)
- # calva (44)
- # cider (82)
- # clojure (21)
- # clojure-greece (1)
- # clojure-losangeles (1)
- # clojure-spec (8)
- # clojure-uk (3)
- # clojurescript (55)
- # community-development (26)
- # cursive (18)
- # datomic (7)
- # editors (6)
- # events (1)
- # fulcro (19)
- # kaocha (1)
- # klipse (1)
- # off-topic (13)
- # re-frame (1)
- # ring-swagger (2)
- # spacemacs (2)
- # vim (15)
Has anyone got any good resources on general AWS stuff that would be applicable to ions? I’d love to read up a bit more from sources other than the docs that anyone would recommend.
I am working on a problem that i've never solved using a database before because I've always had this state locally. Let's say I have a "worker-entity" with a :worker/current-jobs-counter attribute. Whenever I start a job I will pick a worker where current-jobs-counter is below 10, and increment it by 1. Would that include a transaction function in datomic?
You can do this with a transaction function: transaction function essentially have a lock on the entire database so there's no possibility of stale reads or conflicts.
But you may also be able to do it with speculative writes that retry if a conflict was detected. Maybe you can use the builtin cas (check and swap) transaction function: https://docs.datomic.com/on-prem/transactions.html#dbfn-cas https://docs.datomic.com/cloud/transactions/transaction-functions.html#sec-1-2
i guess a transaction function in the cloud becomes a ion
No worries, I am very thankful for your replies. Made some good progress conceptually 🙂