Clojurians Log v2

We have an api at work, where the transport is http://socket.io(which I don't particularly like, but provides a unified abstraction over websockets and long polling), and the api is defined as a graphql endpoint

Graphql is ok, and it gives you some bounds and lets you talk about synchronous request/response kind of messages and asynchronous subscription kinds of messages

The server side is using lacinia to process the graphql

An alternative would be to look at something like grpc's service (server?) language, which I guess is actually part of the protocol buffer language, buy let's you describe a service as a collection of kind of rpc calls with some asynchronous streaming stuff

https://gist.github.com/hiredman/60e5e6f0025cb38c8a7739d21f5a8ce6 is an idea I had but havent pursued too deeply, which describes a (stateful) api as a collection of specs for messages, and states where those messages are valid, inspired by ubf

I didn't know graphql had support for subscriptions. that's pretty cool. looking at the lacina docs for them now.

Will also look into grpc and that gist, thanks!

What do you think about this project? https://dqlite.io/ Distributed SQLite. I always like SQLite for it easiness, and that would be great to use in smaller applications [it would be great with datahike].

It has a jepsen test, so it looks like a serious effort 😃 https://github.com/canonical/jepsen.dqlite

I tried to understand how it worked, but from my understanding, they launch the golang app and test it from there. It did not manage to understand how you could use it though xD. I wished I was smart enough to try to develop against the wire protocol,

Plus the jepsen code is in Clojure haha

Happy new year everyone :)

Happy 2021!