You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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
The text was updated successfully, but these errors were encountered: