This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-07-31
Channels
- # announcements (1)
- # beginners (171)
- # cider (51)
- # clj-kondo (40)
- # cljsrn (5)
- # clojure (68)
- # clojure-dev (42)
- # clojure-europe (2)
- # clojure-italy (20)
- # clojure-spec (2)
- # clojure-uk (141)
- # clojurescript (19)
- # community-development (4)
- # core-async (17)
- # core-logic (3)
- # cursive (11)
- # data-science (1)
- # datomic (7)
- # defnpodcast (2)
- # figwheel (9)
- # figwheel-main (2)
- # fulcro (15)
- # graphql (21)
- # jackdaw (3)
- # joker (11)
- # juxt (1)
- # luminus (12)
- # off-topic (2)
- # pathom (73)
- # pedestal (2)
- # re-frame (41)
- # reagent (14)
- # reitit (4)
- # shadow-cljs (39)
- # tools-deps (4)
as a backend? Take a look at lacinia: https://lacinia.readthedocs.io/en/latest/
I really like it as a library
well; I can only compare lacinia against the graphql-ruby library. What I like in lacinia is that the schema is ‘just data’ and that schema & resolvers are properly seperated
This; unlike the ruby implementation, allows for easy (unit) testing of resolvers as they are just functions & reuse of resolvers if you wanted to
sorry; what do you mean?
we (= at my company) are using Lacinia in our Clojure backends. We have both JavaScript as well as ClojureScript consumers of this GraphQL API.
(i’ve never understood why clojure didnt get adopted fully by big companies, i even heard of some going away from it )
well, the one I work at. Lacinia itself is product of Walmart Labs and I believe is used in production there. But don’t quote me on that 🙂
Walmart uses and maintains Lacinia. We use it in production, around 17K req/minute right now.
@U04VDKC4G fellow lewis. how has it been hiring clojure dev at walmart