Here is the code for the parser

(def parser
  (p/async-parser
   {::p/env     {::p/reader               [p/map-reader
                                           pc/async-reader2
                                           pc/ident-reader
                                           p/env-placeholder-reader]
                 ::p/placeholder-prefixes #{">"}}
    ::p/mutate  pc/mutate-async
    ::p/plugins [(pc/connect-plugin {::pc/register app-registry})
                 p/error-handler-plugin
                 p/trace-plugin
                 params-down-pathom-plugin]}))

The code for the ring handler

(defn query
  [query]
  (let [params (clojure.walk/keywordize-keys (:params query))
        q (:query params)]
    (println "ring query" q)
    ; (println (crux-api/get-concept-translations-by-jurisdiction 1 (rand-nth (range 730 750))))
    {:status 200
     :body
     (encode-transit-json
      (<!! (parser params (clojure.edn/read-string q))))}))

The code for the resolver that only work "sometime"

(pc/defresolver by-jurisdiction-id [{:keys [] :as env} params]
                {::pc/input #{:translation/query}
                 ::pc/output [:translations
                              [:translation/id
                               :translation/language
                               :translation/value
                               :translation/status
                               :jurisidction/id
                               :concept/id
                               :app/type]]}
                (let [query (parse-query-params env)
                      jurisdiction-id (:jurisdiction/id query)
                      concept-id (:concept/id query)
                      results (crux-api/get-concept-translations-by-jurisdiction)]
                    {:translations []}))

and the crux function

(defn get-concept-translations-by-jurisdiction
  [jurisdiction-id concept-id]
  (let [ids (crux/q
             (crux/db node)
             {:find '[typ]
              :where '[[e :app/type typ]
                       [e :jurisdiction/id jurisdictionid]
                       [e :concept/id conceptid]]
              :args [{'jurisdictionid jurisdiction-id
                      'conceptid concept-id}]})]
    (println ids)
    []))

Hi 🙂 Is your crux function really meant to be returning only [] on that last line of the let?

No it is only for tests

If i remove the crux call it works

if i call the crux function from the ring handler it works too

That's only in the resolver

but if i remove the crux call in the resolver, it works too

Here is the crux conf

(defonce node
  (crux/start-node
   {:crux.node/topology :crux.standalone/topology
    :crux.node/kv-store "crux.kv.lmdb/kv"
    :crux.standalone/event-log-dir "resources/data/eventlog-1"
    :crux.kv/db-dir "resources/data/db-dir-1"
    :crux.standalone/event-log-kv-store "crux.kv.lm/kv"}))

(defonce db (crux/db node))

@U899JBRPF Do you think i am correct with crux ?

It seems waiting the previous query close or seomthing like this ?

I can't see anything obviously wrong with what your doing with Crux. Except I'm not sure what this line is for:

(defonce db (crux/db node))

it was a try otherwise i did start with (crux/db node) but the problem is the same Do i have to start and close the node for each ring request ?

Ah okay. And no, that definitely shouldn't be necessary 🙂

Is it possible to reproduce with a minimal example in a gist or repo that you can share? I think that would be easier to debug both for people here and also the folks over on #pathom

Hi Jeremy, many thanks ! I did a little project as you suggested but no error there. So the problem should come from somewhere else. I continue to search ... Thansk !

Ok the problem was that i had two resolvers that return the same signature ...

Sorry for the derangement and many thanks for your help

ahhh - glad I could help a little bit 😀

well done for persevering, at least you won't make that mistake again!

This is great stuff - thanks for sharing your work and ideas so generously in return! By the way, we have a new event bus API merged and ready for the next release so you won't have to do your own polling 🙂

perfect, I can't wait to try it out!

This is cool 🙂 just wondering why Crux was choosen over Datahike?

I haven't used Datahike, but it seems to still be at an early/experimental stage, whereas Crux is more mature. With Crux I'm not worried about hitting a wall when I need scale since I know I can switch to Kafka for the storage backend. Having Juxt behind it is also a plus.

Here's a relevant snippet from https://github.com/replikativ/datahike#when-should-i-pick-what: > Pick datahike if your app has modest requirements towards a typical durable database, e.g. a single machine and a few millions of entities at maximum. > Pick Datomic if you already know that you will need scalability later In this case, s/Datomic/Crux/. IMO Crux gives you the best of both worlds: you can run it on the local filesystem for dev and small deployments, for small to medium size you can use managed SQL, and for large deployments you can use Kafka

Got it! I see that datahike extends datascript which is well done. So by choosing Crux also means not choosing to use datascript or is there a way to leverage the power of datascript ? The below article* reads that datascript+crux is not that viable(for now) as much as in datascript+datahike. *https://opencrux.com/docs#queries_datascript_differences

Crux implements its own version of datalog (whereas datascript's datalog is very close to Datomic's datalog). So you can't use datascript's datalog from Crux, but you can still use datalog which is the important thing.