Datomic Cloud instance suddenly giving

{
  "errorMessage": "Connection refused",
  "errorType": "datomic.ion.lambda.handler.exceptions.Unavailable",
  "stackTrace": [
    "datomic.ion.lambda.handler$throw_anomaly.invokeStatic(handler.clj:24)",
    "datomic.ion.lambda.handler$throw_anomaly.invoke(handler.clj:20)",
    "datomic.ion.lambda.handler.Handler.on_anomaly(handler.clj:171)",
    "datomic.ion.lambda.handler.Handler.handle_request(handler.clj:196)",
    "datomic.ion.lambda.handler$fn__3841$G__3766__3846.invoke(handler.clj:67)",
    "datomic.ion.lambda.handler$fn__3841$G__3765__3852.invoke(handler.clj:67)",
    "clojure.lang.Var.invoke(Var.java:399)",
    "datomic.ion.lambda.handler.Thunk.handleRequest(Thunk.java:35)"
  ]
}

@brian.rogers can you log a case by emailing <mailto:[email protected]|[email protected]>? I would like to gather more information on this failing service before offering concrete next steps and it would be best to share that information over a case. Useful starting info: -Cft version. -solo or prod? -other services are working? -did you deploy before the error? Anything change before you saw this error?

@jaret I just redeployed master and it's fixed itself. Would it be useful for me to still submit a case to cognitect?

If it helps: cft version I don't know (what is cft?), solo topology, we only are running that one datomic service so I couldn't test anything else, lat deployment was in the summer and it's been running ever since until a day or two ago

Yes. I am very interested in tracking this down and would like to provide you potential steps to gather a thread dump should this issue occur again.

CFT = cloud formation template version, found in the outputs of your compute stack

@brian.rogers obviously no urgency on the case, but if you get a chance please do log one. If we have a bug here I’d like to address it.

Sure thing!

has anyone used datascript as a client-side cache for datomic?

I think you'd be surprised how different they are.

(Meaning, I was)

in that semantically they are too different for datascript to act as a cache that way?

the reason I’m asking is because I’ve been thinking about building a datalog API in front of our microservices (a la GraphQL), and started thinking that it might make sense to use datascript as a client-side cache to reduce the queries that have to actually hit the backend. my thinking was that a query could respond with not only the result, but the datums that were resolved in the processing of the query. that way the client side could transact those into a client-side cache and future queries could potentially query the local db instead of sending a request to the server. however, populating the cache for a query could end up accidentally being quite a lot of datums that need to be sent over the wire, even if the query result is small. so I was wondering if this same idea had been solved by some datomic <-> datascript integration.

So, at that point you're putting your database on the internet.

(If i'm understanding you correctly)

I’m not sure what you mean by that.

What is the first problem (the a la GraphQL) you're trying to solve? Why are you interested in building the datalog api? What brought you to the conclusion of "use datascript as a client-side cache"? What are you interested in caching?