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
The CRDT pr enables high availability of the ledger store, however to get high availability of the actual object/bucket data, TemporalX's replication feature needs to be use. It might be worth enabling "automatic management" of the replication.
One possible implementation would be a background worker process that whenever the ledger is updated, it would update a replication file with the new CID(s), sign it, and publish it. This should be the most efficient option, however there might be a slight delay between the time the ledger is updated, and replication worker picks it up
The faster solution would be that whenever we finish storing the data for the request, we launch a goroutine to handle the replication update broadcast, and then we return the response to the user.
The text was updated successfully, but these errors were encountered:
The CRDT pr enables high availability of the ledger store, however to get high availability of the actual object/bucket data, TemporalX's replication feature needs to be use. It might be worth enabling "automatic management" of the replication.
One possible implementation would be a background worker process that whenever the ledger is updated, it would update a replication file with the new CID(s), sign it, and publish it. This should be the most efficient option, however there might be a slight delay between the time the ledger is updated, and replication worker picks it up
The faster solution would be that whenever we finish storing the data for the request, we launch a goroutine to handle the replication update broadcast, and then we return the response to the user.
The text was updated successfully, but these errors were encountered: