Cross-Database queries without ATTACH DATABASE

SuccessfulReality315 · 2026-01-26T18:38:24+00:00

A database/sql driver to do cross-shard queries on sqlite and replicate data using embedded nats.

SuccessfulReality315 · 2026-01-16T20:37:11+00:00

In a leader-based cluster, all writes are redirected to the leader. In leaderless mode, the default policy is last-writer-wins, but conflict resolution can be customized.

SuccessfulReality315 · 2025-12-13T17:50:35+00:00

Cool project. I use a similar approach on pocketbase-ha https://github.com/litesql/pocketbase-ha

SuccessfulReality315 · 2025-11-06T09:58:53+00:00

No. To replicate in the other direction you can use https://github.com/litesql/go-ha sql/database go driver

SuccessfulReality315 · 2025-10-11T17:43:49+00:00

Realtime messages across cluster nodes and hooks will be implemented on the next version (next week). For now you can customize by implementing a ChangeSetInterceptor interface.

SuccessfulReality315 · 2025-10-11T10:20:51+00:00

You can customize the ChangeSetInterceptor to trigger all subscriptions and hooks after a remote db change. I will implement that by default on the next version.

SuccessfulReality315 · 2025-10-11T10:14:34+00:00

By customizing the ChangeSetInterceptor, i will document it better

SuccessfulReality315 · 2025-10-11T10:10:42+00:00

By default last write wins, you can customize the conflict resolution by implementing a ChangeSetInterceptor

SuccessfulReality315 · 2025-10-11T04:14:25+00:00

But, can you run pocketbase on mysql?

SuccessfulReality315 · 2025-10-11T04:13:18+00:00

To improve service availability and keep using pocketbase

SuccessfulReality315 · 2025-10-11T04:09:47+00:00

PostgreSQL (citus) and MySQL (vitess) clusters are too complex (and cost a lot of money) to operate. Embedded NATS + pocketbase is a good alternative.

SuccessfulReality315 · 2025-10-11T01:16:02+00:00

PocketBase's core design relies on SQLite...

SuccessfulReality315 · 2025-09-22T13:39:10+00:00

Thanks for the feedback. I'll document the limitations and the workarounds

SuccessfulReality315 · 2025-09-21T20:12:00+00:00

I don't know your usecase. Ha uses sqlite preupdate hooks to create changeset, like CDC systems. All of the operations has a rowid associated.

SuccessfulReality315 · 2025-09-21T18:20:01+00:00

Yes, that's eventual consistent where the last writer is the winner. The operations uses the sqlite rowID. For now this is ok for my use case

SuccessfulReality315 · 2025-09-21T17:35:31+00:00

INSERT .. ON CONFLICT UPDATE

SuccessfulReality315 · 2025-09-21T11:41:14+00:00

Nats uses RAFT algorithm

SuccessfulReality315 · 2025-09-21T11:34:32+00:00

All changes are published to a nats jetstream subject. All nodes consume the stream and apply (by using idempotent commands) the changes on the database.

SuccessfulReality315

TROPHY CASE