This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-04-23
Channels
- # beginners (8)
- # boot (87)
- # cider (16)
- # cljs-dev (1)
- # cljsrn (2)
- # clojure (27)
- # clojure-austin (2)
- # clojure-beijing (1)
- # clojure-belgium (1)
- # clojure-russia (66)
- # clojure-uk (17)
- # clojurescript (48)
- # core-typed (1)
- # cursive (3)
- # datomic (8)
- # emacs (7)
- # funcool (3)
- # hoplon (22)
- # instaparse (1)
- # jobs-discuss (4)
- # leiningen (2)
- # om (17)
- # onyx (16)
- # reactive (2)
- # reagent (7)
- # rum (2)
- # specter (1)
- # untangled (3)
@mccraigmccraig One of the reasons I want to move to microservices is to allow for language experimentation
hmm... that's actually a good reason for microservices
@otfrom: how do you answer the question of connecting / discovering all these microservices?
eventbus or console/elb/dns
atm i connect services with known service-ports and haproxy everywhere configured from the marathon api (which knows where actual service containers are listening)... a more primitive version of https://github.com/mesosphere/marathon-lb/blob/master/README.md ... works pretty well
i’ve had decent success with just using config files to say where other services live, and letting chef use searches to “discover” services / load balancer endpoints
Eventbus on kineses looks good for me.
I suspect that using a event broker (whether it is Kafka or MQTT depends on requirements) is much nicer then using HTTP.
this is the other one https://github.com/ymilky/franzy