there’s GitHub - rbino/tigerbeetlex: An Elixir client for TigerBeetle · GitHub

Currently TigerBeetlex returns its own structs (i.e. TigerBeetlex.Account, TigerBeetlex.Transfer etc), while to use Ash.DataLayer.Simple I guess you have to define structs as resources from the Ash side and return those. That’s why in my ElixirConf talk I’ve cited user-defined structs first as next step in TigerBeetlex before doing any kind of Ash interaction.

Although for a quick and dirty test one might also define an Ash resource with the same attributes as TigerBeetlex.Account and just replace the __struct__ field.

They don’t have an Elixir client and I don’t think they have a documented wire protocol, so either you need to ask them to create one or you need to embed another client in Elixir.

Poking around in their repo they seem to have a C client but it has no docs and is not listed in their docs, so I think it’s probably for internal use. There also seems to be a WIP Rust client which would be a good candidate for a NIF when it’s finished.

Another option would be to create a proxy application (in say Go or Java) which accepts API calls from Elixir and delegates them to the actual client. People used to do this with FoundationDB because their client is very, uh, particular.