This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-10-26
Channels
- # 100-days-of-code (1)
- # aleph (4)
- # beginners (112)
- # boot (2)
- # business (4)
- # calva (3)
- # cider (37)
- # clara (26)
- # cljs-dev (6)
- # cljsrn (1)
- # clojars (4)
- # clojure (89)
- # clojure-brasil (1)
- # clojure-conj (1)
- # clojure-dev (81)
- # clojure-dusseldorf (8)
- # clojure-italy (41)
- # clojure-nl (3)
- # clojure-spec (11)
- # clojure-uk (14)
- # clojurescript (73)
- # cursive (1)
- # data-science (3)
- # datomic (2)
- # dirac (9)
- # duct (6)
- # emacs (4)
- # figwheel-main (1)
- # fulcro (47)
- # incanter (3)
- # jobs-discuss (43)
- # leiningen (18)
- # luminus (6)
- # lumo (4)
- # mount (4)
- # off-topic (31)
- # portkey (8)
- # protorepl (5)
- # re-frame (9)
- # reagent (15)
- # reitit (2)
- # ring-swagger (7)
- # shadow-cljs (28)
- # specter (4)
- # tools-deps (8)
- # uncomplicate (1)
I’m considering Duct for an upcoming project and I’m wondering if there are any performance concerns I should be aware of. I haven’t seen any comparisons with other frameworks. Moreover, I haven’t decided on a routing library yet (open to suggestions), which I’m sure is the biggest consideration here. The project isn’t particularly performance sensitive, but just checking.
The only performance impact Duct should have is on startup, and that should be fairly minimal compared to the time spend loading all required Clojure files.
I’ve created a Duct module for Bidi https://github.com/druids/duct.module.bidi. As you can see it’s easy to create it for any other routing library.
You can use Duct regardless of which routing library you choose (default uses compojure or ataraxy); I personally use it with Pedestal and it’s routing libraries. So there’s no “lock-in” that you can’t get around if you later have metrics showing that routing is your bottleneck.