Add support for rqlite/rqlite

[shanduur]

Is there an existing issue for this?

• I have searched the existing issues

Feature description

Right now we have support for Postgres and MySQL. This gives us opportunity to use other databases that are compatible with those two, like CockroachDB, TiDB and Yugabyte.

However most of them are hard to deploy and quite resource heavy. Using rqlite/rqlite can bring benefits like:

• fault-tolerant,
• replication,
• very easy installation, deployment, and operation

What would the ideal solution look like to you?

Adding new supported backend (rqlite), that can be configured as easy as other backends.

Anything else?

No response

[charithe]

Hi, thanks for suggesting rqlite. Personally, I'd like to support it as well but it currently doesn't have a database/sql driver -- which complicates things for us because we have to build a custom driver for it rather than reusing our common database code.

You could use Cerbos' SQLite driver with Litestream for replication and disaster recovery. It does require some setup work on your end to replicate/restore the database but Cerbos should "just work" with it.

[shanduur]

As you can see in the rqlite/gorqlite README - Why not a database/sql driver?, database/sql driver is not possible given the rqlite design. However their API is mature enough, and uses concepts similar to database/sql, so writing new driver should be quite easy (although don't quote me on that 😆)

[charithe]

Yeah, I understand why they need a different driver. It's just that we are a really small team and having to implement, test and maintain a separate code path, keeping up-to-date with upstream API changes and providing support for users is quite a big commitment.

I am keeping this issue open because I'd like to add support for rqlite at some point. It's unlikely that it will happen in the near future though.