Fork me on GitHub
#graphql
<
2019-07-31
>
lewix21:07:18

How’s graphql with clojure, coming from node?

Lennart Buit21:07:19

I really like it as a library

lewix21:07:22

i see so it’s functional and working well

lewix21:07:30

any disadvantage vs advantage?

Lennart Buit21:07:29

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

💯 4
Lennart Buit21:07:16

This; unlike the ruby implementation, allows for easy (unit) testing of resolvers as they are just functions & reuse of resolvers if you wanted to

lewix21:07:36

hmm interesting

lewix21:07:54

is that a web app fully clojure?

Lennart Buit21:07:16

sorry; what do you mean?

Lennart Buit21:07:25

we (= at my company) are using Lacinia in our Clojure backends. We have both JavaScript as well as ClojureScript consumers of this GraphQL API.

lewix21:07:32

is that a company you work for or yours?

lewix21:07:34

(i’ve never understood why clojure didnt get adopted fully by big companies, i even heard of some going away from it )

Lennart Buit21:07:35

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 🙂

hlship22:07:30

Walmart uses and maintains Lacinia. We use it in production, around 17K req/minute right now.

lewix17:08:03

@U04VDKC4G fellow lewis. how has it been hiring clojure dev at walmart

hlship17:08:08

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.