Clojurians Log v2
graphql
How’s graphql with clojure, coming from node?
wow
@hlship fellow lewis. how has it been hiring clojure dev at walmart
We have a pretty intensive hiring process, that includes take home work and a half day of remote pairing. We ended up with some great candidates, and then had to deal with the painful process of narrowing it down to the two slots we had open.
as a backend? Take a look at lacinia: https://lacinia.readthedocs.io/en/latest/
I really like it as a library
i see so it’s functional and working well
any disadvantage vs advantage?
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
1💯i see
This; unlike the ruby implementation, allows for easy (unit) testing of resolvers as they are just functions & reuse of resolvers if you wanted to
hmm interesting
is that a web app fully clojure?
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.
is that a company you work for or yours?
(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 🙂
i see
haha
Walmart uses and maintains Lacinia. We use it in production, around 17K req/minute right now.