Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Db scale out of SQLite using NATS #16

Open
gedw99 opened this issue Apr 8, 2024 · 2 comments
Open

Db scale out of SQLite using NATS #16

gedw99 opened this issue Apr 8, 2024 · 2 comments

Comments

@gedw99
Copy link

gedw99 commented Apr 8, 2024

I would like to suggest https://github.com/maxpert/marmot be considered as a SQLite db scale out approach.

It uses NATS and so it’s a nice synergy for the nats kv provider.

Marmot is currently used for SQLite Db.
It provides a multi master strategy at the moment, using a LWW ( last write wins ) strategy. There are some trade offs with this like any multi master scenario.

This will mean that all instances of caddy can have a db, so any downtime of any instance will not affect the global system. When it comes back up it will catchup.

New instances will also catchup I believe.

DB Schema migrations are not yet part of marmot. There is an issue for it.

it’s currently used with pocketbaae too. I have run it and it worked well.

please let me know how you feel about this @infogulch

@infogulch
Copy link
Owner

That looks cool. I'm not sure if xtemplate needs to do anything in particular to enable this, it should work out of the box given that marmot is a sidecar process.

@gedw99
Copy link
Author

gedw99 commented Apr 19, 2024

true.

Maybe add it to the README or some pertinent area of the docs.

SQLITE and scalout / backup is a common need.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants