This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-02-01
Channels
- # aleph (1)
- # announcements (2)
- # aws (3)
- # bangalore-clj (1)
- # beginners (136)
- # boot (3)
- # calva (89)
- # cider (44)
- # cljdoc (1)
- # cljs-dev (31)
- # clojure (101)
- # clojure-europe (3)
- # clojure-italy (52)
- # clojure-nl (7)
- # clojure-spec (12)
- # clojure-uk (34)
- # clojurescript (62)
- # community-development (46)
- # cursive (25)
- # datomic (6)
- # duct (26)
- # events (6)
- # figwheel-main (4)
- # fulcro (25)
- # graphql (2)
- # jackdaw (4)
- # jukebox (3)
- # kaocha (57)
- # leiningen (31)
- # off-topic (3)
- # onyx (4)
- # other-languages (22)
- # pathom (18)
- # re-frame (9)
- # reitit (3)
- # shadow-cljs (60)
- # spacemacs (9)
- # speculative (22)
- # sql (39)
- # tools-deps (45)
- # vim (37)
Don't know much about golang for an API gateway it might be better than clojure, any thoughts? https://www.infoq.com/articles/api-gateway-clojure-golang
@gklijs To be completely honest I would never expect Clojure to do better performance-wise on such tasks than Go.
I’m pretty sure most people don’t pick Clojure for performance, but for other reasons
Well, I'm a big fan of blocking ops, from a code layout perspective. But I doubt core-async can really be a full replacement for golang, in terms of bare metal performance for non-blocking ops, interleaving continuations and whatnot.
choice supportive bias, confirmation bias, expectation bias, illusion of validity, insensitivity to sample size, and post-purchase rationalization are all biases at work in that kind of comparison, which leaves out the big one, if you initiate a large rewrite that takes many person hours, you better have something to show for it
blog posts along the lines of "our company rewrote X in Y and Y is better" are interesting sometimes, but can never really convincingly argue their thesis
> The fact that the API gateway is now built in a typed language provides the ability to plug in diverse functionalities and introduce new technologies much more easily with Golang’s library support and community
Every rewrite benefits from the fact that you now understand the system better than you did when starting writing the previous version.
That's something that crossed my mind. We currently work with a code base several years old, with none of the developers working on it longer than a year. Even a rewrite in the same language/framework would already improve much.
(speaking from experience as we're rolling out the 3rd gen of our platform which is essentially the 2nd complete rewrite from the ground up!)