maxohq / surrealix

A lean and correct Elixir SDK for SurrealDB
MIT License
15 stars 0 forks source link
database elixir surrealdb websocket

Surrealix

CI Hex.pm Docs Total Download License


Lightweight, correct and up-to-date Elixir SDK for SurrealDB.

Why use Surrealix?

Usage

# {:ok, pid} = Surrealix.start_link(debug: [:trace]) ## for debugging!
{:ok, pid} = Surrealix.start_link()
Surrealix.signin(pid, %{user: "root", pass: "root"})
Surrealix.use(pid, "test", "test")
Surrealix.query(pid, "SELECT * FROM person;")
Surrealix.query(pid, "SELECT * FROM type::table($table);", %{table: "person"})
## Example with live query callbacks
Surrealix.live_query(pid, "LIVE SELECT * FROM user;", fn data, query_id ->
  IO.inspect({data, query_id}, label: "callback")
end)

## Example with live query with DIFF
Surrealix.live_query(pid, "LIVE SELECT DIFF FROM user;", fn data, query_id ->
  IO.inspect({data, query_id}, label: "callback")
end)

# inspect currently registered live queries
Surrealix.all_live_queries(pid)

Handling reconnection

To properly deal with connection drops, provide an on_auth-callback when starting a Surrealix Socket. on_auth callbacks should include logic to authenticate the connection and select a namespace / database.

This callback is called in a non-blocking fashion, so it is important to wait until the on_auth-callback is finished. This is done via Surrealix.wait_until_auth_ready(pid) function, that checks auth status via busy-waiting.

Live queries that were setup via Surrealix.live_query(pid, sql, callback) function are registed on SocketState and will be re-established after a successful reconnection.

{:ok, pid} =
    Surrealix.start(
      on_auth: fn pid, _state ->
        IO.puts("PID: #{inspect(pid)}")
        Surrealix.signin(pid, %{user: "root", pass: "root"}) |> IO.inspect(label: :signin)
        Surrealix.use(pid, "test", "test") |> IO.inspect(label: :use)
      end
    )

# blocks until the `on_auth` callback is executed
Surrealix.wait_until_auth_ready(pid)

# now we can execute queries, that require auth
Surrealix.live_query(pid, "LIVE SELECT * FROM user;", fn data, query_id ->
  IO.inspect({data, query_id}, label: "callback")
end)

Surrealix.live_query(pid, "LIVE SELECT * FROM person;", fn data, query_id ->
  IO.inspect({data, query_id}, label: "callback")
end)

Telemetry

Currently library publishes only 3 events:

events = [
  [:surrealix, :exec_method, :start],
  [:surrealix, :exec_method, :stop],
  [:surrealix, :exec_method, :exception]
]

In the meta there is further information about the method name and the arguments, that were sent to SurrealDB server.

As example we provide a Surrealix.Telemetry.Logger, that logs those events to the console.

## Configure basic logger telemetry
Surrealix.Telemetry.Logger.setup()

Configuration

## in config.exs / runtime.exs file
config :surrealix, backoff_max: 2000
config :surrealix, backoff_step: 50
config :surrealix, timeout: :infinity # default 5000
config :surrealix, :conn,
  hostname: "0.0.0.0",
  port: 8000

Installation

If available in Hex, the package can be installed by adding surrealix to your list of dependencies in mix.exs:

def deps do
  [
    {:surrealix, "~> 0.1"}
  ]
end

Documentation can be generated with ExDoc and published on HexDocs. Once published, the docs can be found at https://hexdocs.pm/surrealix.

Aknowledgements

Code foundation was taken from https://github.com/joojscript/surrealdb_ex. Since this package has not received any commits in the last 7 months (2023-10-31) and the issues are left uncommented, I have assumed that the maintainer is not interested in any contributions.

Ref

Support

Sponsored by Quantor Consulting

License

The lib is available as open source under the terms of the MIT License.