This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-11-02
Channels
- # admin-announcements (1)
- # aws-lambda (9)
- # beginners (161)
- # boot (1)
- # cider (3)
- # cljsrn (36)
- # clojure (245)
- # clojure-austin (2)
- # clojure-denmark (3)
- # clojure-dev (11)
- # clojure-greece (6)
- # clojure-italy (25)
- # clojure-russia (5)
- # clojure-serbia (1)
- # clojure-spec (76)
- # clojure-uk (78)
- # clojurescript (168)
- # clojurex (4)
- # community-development (7)
- # core-async (11)
- # core-logic (5)
- # css (6)
- # cursive (8)
- # data-science (6)
- # datomic (5)
- # devops (4)
- # duct (17)
- # emacs (1)
- # figwheel (8)
- # fulcro (51)
- # hoplon (4)
- # instaparse (3)
- # kekkonen (6)
- # klipse (3)
- # lein-figwheel (9)
- # luminus (2)
- # lumo (3)
- # midje (4)
- # off-topic (11)
- # om (4)
- # onyx (62)
- # other-languages (60)
- # re-frame (21)
- # reagent (63)
- # rum (1)
- # shadow-cljs (22)
- # spacemacs (22)
- # specter (23)
- # test-check (2)
- # vim (2)
- # yada (6)
We had some issuses with the update calls in faraday, but otherwise it worked. I think we'd have done a SQL db in the end after we abandoned event sourcing.
All this seems to cry out for a wiki or github repo with common use cases for lambda documented (ie. in cljs and in clj, using ring-aws-lambda-middleware versus lambada versus portkey, with or without api gateway integration, REST apis versus AWS events sourcing. etc). Or does something like that exist?
… which is not to say “let’s make an opinionated framework” and also not necessarily “let’s capture all this in a leiningen or boot template that people can just use…”
Yeah the guys at nervous-systems did an excellent job, basically everything i have used that actually worked for cljs was their stuff.
That being said the use case the lein template imagines was a bit more all emcompassing thing i actually use