This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-02-23
Channels
- # announcements (2)
- # atom-editor (3)
- # babashka (49)
- # beginners (100)
- # biff (9)
- # calva (78)
- # clj-kondo (18)
- # clojure (143)
- # clojure-europe (13)
- # clojure-germany (1)
- # clojure-nl (2)
- # clojure-spec (5)
- # clojure-sweden (2)
- # clojure-uk (4)
- # clojurescript (58)
- # conjure (1)
- # cursive (4)
- # datascript (11)
- # datomic (63)
- # docker (7)
- # emacs (18)
- # events (1)
- # fulcro (18)
- # graalvm (5)
- # helix (4)
- # improve-getting-started (13)
- # jobs (4)
- # jobs-discuss (3)
- # lsp (15)
- # malli (90)
- # membrane (14)
- # off-topic (12)
- # other-languages (5)
- # pedestal (7)
- # polylith (53)
- # re-frame (15)
- # reitit (23)
- # releases (4)
- # remote-jobs (9)
- # ring (11)
- # shadow-cljs (90)
- # specter (2)
- # testing (3)
- # tools-build (63)
- # vim (2)
- # xtdb (8)
Is there a way, for a set of routes, to apply rate-limiting or lower priority or just confine them to a fixed number of threads so that they don't overrun the server? We're using jetty...
if they've made it into your routes, jetty is already handling them you may want to consider a rate-limiting load balancer in front of your service (e.g. API Gateway)
in-app rate limiting makes sense IMO, if the resource being rate-limited isn't jetty itself e.g. if some route guards some special resource, maybe you want to rate-limit that specific resource
I should probably look into jetty specifically, and see if it can do basic routing and strategies like this before handing over to pedestal itself. Eg a different queuing/buffering strategy.