This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-04-27
Channels
- # aleph (1)
- # aws (2)
- # beginners (69)
- # boot (79)
- # braid-chat (1)
- # cider (221)
- # clara (13)
- # cljs-dev (9)
- # cljs-edn (1)
- # cljsrn (7)
- # clojure (128)
- # clojure-chicago (1)
- # clojure-russia (196)
- # clojure-sanfrancisco (1)
- # clojure-uk (13)
- # clojurescript (166)
- # community-development (2)
- # css (2)
- # cursive (8)
- # datomic (4)
- # emacs (11)
- # hoplon (54)
- # instaparse (2)
- # jobs (16)
- # jobs-discuss (54)
- # jobs-rus (7)
- # luminus (4)
- # off-topic (33)
- # om (37)
- # onyx (8)
- # proton (10)
- # quil (8)
- # re-frame (29)
- # reagent (7)
- # remote-jobs (2)
- # untangled (140)
- # yada (1)
@martintrojer: interested in your experience with Cass. I've recently carried out a proof of concept around non functional reqts with HBase and found exactly same issues. I came to same conclusion that cluster needed to be much large w/ a lot more redundancy to cope with high write alongside reads. PoC finished before I had chance to test theory though!
Getting an even split of data across region servers also made a huge difference but it was very delicate balance and different data profiles made huge difference
Getting an even split of data across region servers also made a huge difference but it was very delicate balance and different data profiles made huge difference
Yeah, and why put you though all that pain when you can just use Dynamo?
Its like RDS just removed all the pain of setting up PSQL read/write slaves etc
martintrojer: I suppose the difference between RDS and Dynamo is that Postgres is Postgres (and you can get it other places). Dynamo is not Cassandra (or anything else). Not a reason against it, but a trade off to think about.
agreed
its a cracking service none the less
moning
G'day everyone 👋